CVE-2026-63132: OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- No fix version is held. The CNA's first reference is the place to look: github.com
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
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.
- weakness
- CWE-208: Observable Timing Discrepancy
- affected
- openbao
- versions
- No affected-version range in held sources.
- fixed in
- No fix version in held sources.
- fixed by package (from OSV advisories)
- openbao (Bitnami): 2.6.0 BIT-openbao-2026-63132github.com/openbao/openbao (Go): 0.0.0-20260713141742-763625a20721 GHSA-34fc-gh42-pj53 GO-2026-6553
- later fixes (from OSV advisories)
- github.com/openbao/openbao 0.0.0-20260713141742-763625a20721 is inside a range CVE-2024-8185 (GHSA-g233-2p4r-3q7v) lists as affected. That advisory is fixed in 2.0.3.github.com/openbao/openbao 0.0.0-20260713141742-763625a20721 is inside a range CVE-2024-9180 (GHSA-rr8j-7w34-xp5j) lists as affected. That advisory is fixed in 2.0.3.github.com/openbao/openbao 0.0.0-20260713141742-763625a20721 is inside a range CVE-2025-59043 (GHSA-g46h-2rq9-gw5m) lists as affected. That advisory is fixed in 2.4.1.github.com/openbao/openbao 0.0.0-20260713141742-763625a20721 is inside a range CVE-2025-64761 (GHSA-7ff4-jw48-3436) lists as affected. That advisory is fixed in 2.4.4.github.com/openbao/openbao 0.0.0-20260713141742-763625a20721 is inside a range CVE-2026-45808 (GHSA-v8v8-cm84-m686) lists as affected. That advisory is fixed in 2.5.4.github.com/openbao/openbao 0.0.0-20260713141742-763625a20721 is inside a range CVE-2026-46358 (GHSA-q8cj-789h-vg24) lists as affected. That advisory is fixed in 2.5.4.
- severity
- 9.2 CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- assigned by
- GitHub_M
- published
- 2026-09-23
check us github.com github.com github.com github.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.00 on 2026-09-28 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- No fix version is held. One published by the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2026-63132', '2026-11-01T23:59:59.999999Z', now());