CVE-2026-63132
criticalpriority · track · 0EPSS 0.006 · 50 %ileDEUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · high–critical · 7.2–9.2
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (6)
Products and version ranges known to be affected.
- Go github.com/openbao/openbao< 0.0.0-20260713141742-763625a20721osvUSpkg:golang/github.com/openbao/openbao
advisories (4)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2026-2343OpenBao: Mehrere SchwachstellenDeutsch2026-07-14csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in OpenBao ausnutzen, um seine Privilegien zu erhöhen, Sicherheitsmaßnahmen zu umgehen oder vertrauliche Informationen offenzulegen.
- GHSA-34fc-gh42-pj53OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack2026-09-22ghsa · osvUS
### 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.
- BIT-openbao-2026-63132OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack2026-10-01vendor · osvUS
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.
- GO-2026-6553OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack in github.com/openbao/openbao2026-10-01vendor · osvUS
OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack in github.com/openbao/openbao
also known as (3)
Other names and identifiers for this entity.
- BIT-openbao-2026-63132osv
- GHSA-34fc-gh42-pj53osv
- GO-2026-6553osv
sources
Which sources assert this record, and when.
references (7) nvd
External citations — patches, advisories, analysis.
- https://github.com/hashicorp/vault/blob/main/CHANGELOG.md#203
- https://github.com/openbao/openbao/commit/0f2d90c331f25d1c6cd108638da03f4c7bd949a8
- https://github.com/openbao/openbao/commit/763625a2072103ea9e9122f2a8408e0b988d287a
- https://github.com/openbao/openbao/pull/3388
- https://github.com/openbao/openbao/pull/3472
- https://github.com/openbao/openbao/releases/tag/v2.6.0
- https://github.com/openbao/openbao/security/advisories/GHSA-34fc-gh42-pj53
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan