How severe is GHSA-34fc-gh42-pj53?

No CVSS score has been assigned to GHSA-34fc-gh42-pj53 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-34fc-gh42-pj53?

GHSA-34fc-gh42-pj53 affects the following packages: github.com/openbao/openbao (Go), github.com/openbao/openbao (Go). Ecosystems affected: Go.

How do I fix GHSA-34fc-gh42-pj53?

Update github.com/openbao/openbao to 0.0.0-20260713141742-763625a20721 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-34fc-gh42-pj53 is resolved across your whole dependency graph.

How do I detect GHSA-34fc-gh42-pj53 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openbao/openbao, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-34fc-gh42-pj53 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-34fc-gh42-pj53 actively exploited in the wild?

No public exploit code has been indexed for GHSA-34fc-gh42-pj53 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-34fc-gh42-pj53?

GHSA-34fc-gh42-pj53 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 42th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-34fc-gh42-pj53?

GHSA-34fc-gh42-pj53 is classified as CWE-208 (CWE-208). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-34fc-gh42-pj53 published, and has it been updated?

GHSA-34fc-gh42-pj53 was published on September 22, 2026 and was last updated on October 1, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing AttackGHSA-34fc-gh42-pj53

Fix: openbao/openbao#3388

GHSA-34fc-gh42-pj53 is a CWE-208 vulnerability in github.com/openbao/openbao. A fix is available for github.com/openbao/openbao — see the affected versions and patch details below.

Also known asBIT-openbao-2026-63132CVE-2026-63132GO-2026-6553

Published

Sep 22, 2026

Updated

Oct 1, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-34fc-gh42-pj53.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐹github.com/openbao/openbao🐹github.com/openbao/openbao

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

OpenBao is an open source identity-based secrets management system. Prior to 2.6.0, OpenBao's handleLogicalRecovery path in http/logical.go compared the highly privileged recovery token with ordinary string equality. A remote unauthenticated attacker able to make repeated recovery mode requests and measure response timing could infer the recovery token. The recovered token could then authorize recovery mode operations that read or modify OpenBao data. This issue is fixed in version 2.6.0.

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/openbao/openbao`	all versions	0.0.0-20260713141742-763625a20721`go get github.com/openbao/openbao@v0.0.0-20260713141742-763625a20721`
🐹Go	`github.com/openbao/openbao`	≥ 0.1.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openbao/openbao, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/openbao/openbao to 0.0.0-20260713141742-763625a20721 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-34fc-gh42-pj53 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact When running in the highly privileged recovery mode, OpenBao was vulnerable to a timing attack against the single recovery token. This allowed an attacker to extract the recovery token and use it to perform operations against the OpenBao instance, including reading or modification of data. ### Patches This has been patched in OpenBao v2.6.0.

O3 Security · Impact-Aware SCA

Is GHSA-34fc-gh42-pj53 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works