GHSA-34fc-gh42-pj53 BIT-openbao-2026-63132 CVE-2026-63132 GO-2026-6553

OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack

Critical Go

Severity: 0.0 / 10; Critical · CVSS 4.0
Exploit chance (EPSS): 0.63%; Chance of exploitation in the next 30 days. Higher than 50.14% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-208 Observable Timing Discrepancy
Fix: 0.0.0-20260713141742-763625a20721; Upgrade github.com/openbao/openbao to this version or later

Description

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.

Affected versions

Go

Package	Vulnerable	Fixed in
github.com/openbao/openbao	`< 0.0.0-20260713141742-763625a20721`	`0.0.0-20260713141742-763625a20721`
github.com/openbao/openbao	`>= 0.1.0, <= 1.1.5`	No fix yet
github.com/openbao/openbao	`< 0.0.0-20260713141742-763625a20721` `>= 0.1.0`	`0.0.0-20260713141742-763625a20721`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/openbao/openbao Go → `0.0.0-20260713141742-763625a20721`

go

go get github.com/openbao/openbao@v0.0.0-20260713141742-763625a20721 && go mod tidy

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Attack vector: Network
Attack complexity: High
Attack requirements: Present
Privileges required: None
User interaction: None
Confidentiality (vulnerable system): High
Integrity (vulnerable system): High
Availability (vulnerable system): None
Confidentiality (subsequent systems): None
Integrity (subsequent systems): None
Availability (subsequent systems): None

Weakness

CWE-208: Observable Timing Discrepancy

Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not.

References

Packages

github.com/openbao/openbao

Timeline

Sep 22, 2026 Published
Oct 1, 2026 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-xp3c-3jw3-4vcr OpenBao Skips Stricter Deny Policy for LIST operations	Medium	Also affects github.com/openbao/openbao
GHSA-444v-8vxr-p36h OpenBao Agent Writes Secrets to Stdout	Low	Also affects github.com/openbao/openbao
GHSA-59w7-v8rr-pr4p OpenBao's Templated Policies Allow Privilege Escalation via Wildcard Characters	High	Also affects github.com/openbao/openbao
GHSA-8w8f-r2xv-4q4j OpenBao: Transit secrets engine crashes on key creation with `derived: true` for asymmetric key types	Medium	Also affects github.com/openbao/openbao
GHSA-mwr2-wmgp-crj6 OpenBao's System Backend allows Unauthorized Management of the containing Namespace	Low	Also affects github.com/openbao/openbao
GHSA-c36x-h252-g9x2 OpenBao: Cross-namespace lease revocation/renewal via canonical sys/leases/{revoke,renew} — incomplete fix of CVE-2026-45808	Low	Also affects github.com/openbao/openbao
GHSA-6mwx-4547-5vc9 OpenBao: LDAPi ldaputil (wrong escape func)	Medium	Also affects github.com/openbao/openbao
GHSA-7j6w-vvw2-5f9c OpenBao's Kerberos Auth Method Accumulates Unaccessible Tokens	Medium	Also affects github.com/openbao/openbao

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor