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.
CVE-2026-63132
CRITICALPre-NVD 9.29.2
EchelonGraph scoreLOW confidence
This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
9.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 9.2Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.2
- EG Score
- 9.2(low)
- EG Risk
- 46(Track)EG Risk 46/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity92% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 22, 2026
Last Modified
September 23, 2026
Advisory Details (6)
Auto-updated Sep 23, 2026Patch available. Sources: github, github_pr, github_commit.
generic
vault/CHANGELOG.md at main · hashicorp/vault · GitHub
https://github.com/hashicorp/vault/blob/main/CHANGELOG.md#203github_commit
commit 763625a20721 (openbao/openbao)
Fix landed in openbao/openbao commit 763625a20721 — awaiting tagged release
https://github.com/openbao/openbao/commit/763625a2072103ea9e9122f2a8408e0b988d287agithub_commit
commit 0f2d90c331f2 (openbao/openbao)
Fix landed in openbao/openbao commit 0f2d90c331f2 — awaiting tagged release
https://github.com/openbao/openbao/commit/0f2d90c331f25d1c6cd108638da03f4c7bd949a8github_pr
Switch to constant-time comparison recovery token (#3388)
Fix merged in openbao/openbao PR #3472 on 2026-07-13 — awaiting tagged release
https://github.com/openbao/openbao/pull/3472github_pr
Switch to constant-time comparison recovery token
Fix merged in openbao/openbao PR #3388 on 2026-07-13 — awaiting tagged release
https://github.com/openbao/openbao/pull/3388github Patch Available
OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack · Advisory · openbao/openbao · GitHub
https://github.com/openbao/openbao/security/advisories/GHSA-34fc-gh42-pj53Vendor Advisories for CVE-2026-63132(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-23 19:18 UTCEG score recompute
- 2026-09-23 18:22 UTCEG score recompute▲ 9.20
- 2026-09-23 18:21 UTCMITRE cvelistV5CVSS v3 → 9.2 · CVSS v4 → 9.2
- 2026-09-22 20:45 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-63132?
CVE-2026-63132 is a critical vulnerability published on September 22, 2026. 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…
When was CVE-2026-63132 disclosed?
CVE-2026-63132 was first published in the National Vulnerability Database on September 22, 2026, with the most recent update on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-63132?
CVE-2026-63132 has a CVSS v3 base score of 9.2 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-63132?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63132, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-63132
Is Your Infrastructure Affected by CVE-2026-63132?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.