CVE-2026-63132GO-2026-6553BIT-OPENBAO-2026-63132GHSA-34FC-GH42-PJ53
OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.6.0, 0.0.0-20260713141742-763625a20721
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- openbao openbao
fixed in 2.6.0
- github.com/openbao/openbaoGo
fixed in 0.0.0-20260713141742-763625a20721; From 0.1.0
- github.com/openbao/openbaoGo
fixed in 0.0.0-20260713141742-763625a20721
- github.com/openbao/openbaoGo
From 0.1.0 · through 1.1.5