CRITICAL GitHub
CVE-2026-63132
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.
Affected Products
- go/github.com/openbao/openbao < 0.0.0-20260713141742-763625a20721
- go/github.com/openbao/openbao >= 0.1.0, <= 1.1.5
References
- https://github.com/advisories/GHSA-34fc-gh42-pj53
- https://github.com/openbao/openbao/security/advisories/GHSA-34fc-gh42-pj53
- https://github.com/openbao/openbao/pull/3388
- https://github.com/openbao/openbao/pull/3472
This critical severity vulnerability was published on 2026-09-22 via GitHub. Affected: go/github.com/openbao/openbao < 0.0.0-20260713141742-763625a20721, go/github.com/openbao/openbao >= 0.1.0, <= 1.1.5.
vulnfeed aggregates 13417 vulnerabilities from NVD, CISA KEV,
Ubuntu, Debian, Red Hat, Kubernetes, Exploit-DB, OSS-Security, GitHub and OpenStack — updated every 4 hours.