Answer in brief
CVE-2026-63132 records a Critical severity vulnerability in OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack. The current sources do not mark it as known exploited. The current feed maps github.com/openbao/openbao (go), github.com/openbao/openbao (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps github.com/openbao/openbao (go), github.com/openbao/openbao (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| github.com/openbao/openbaogo | <0.0.0-20260713141742-763625a20721 | 0.0.0-20260713141742-763625a20721 |
| github.com/openbao/openbaogo | >=0.1.0,<=1.1.5 | Not reported |
Published upstream
Sep 22, 2026
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Sep 22, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Sep 22, 2026
### 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.
Quoted source text, attributed separately from HOL analysis.