github.com/openbao/openbao
Affected
- introduced
0, fixed0.0.0-20260713141742-763625a20721(semver)
Fixed versions
0.0.0-20260713141742-763625a20721
Fix
- Fixed version
0.0.0-20260713141742-763625a20721go get github.com/openbao/[email protected]
Advisory
Also known as: BIT-openbao-2026-63132, CVE-2026-63132, GO-2026-6553
OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack
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.
Critical Basis: The source's own band: CRITICAL
0, fixed 0.0.0-20260713141742-763625a20721 (semver)0.0.0-20260713141742-763625a20721
0.0.0-20260713141742-763625a20721go get github.com/openbao/[email protected]0.1.0, last affected 1.1.5 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0