Summary
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
This has been patched in OpenBao v2.6.0.
Frequently Asked Questions
- What is CVE-2026-63132? CVE-2026-63132 is a critical-severity security vulnerability in github.com/openbao/openbao (go), affecting versions < 0.0.0-20260713141742-763625a20721. It is fixed in 0.0.0-20260713141742-763625a20721.
- Which versions of github.com/openbao/openbao are affected by CVE-2026-63132? github.com/openbao/openbao (go) versions < 0.0.0-20260713141742-763625a20721 is affected.
- Is there a fix for CVE-2026-63132? Yes. CVE-2026-63132 is fixed in 0.0.0-20260713141742-763625a20721. Upgrade to this version or later.
- Is CVE-2026-63132 exploitable, and should I be worried? Whether CVE-2026-63132 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-63132 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-63132? Upgrade
github.com/openbao/openbaoto 0.0.0-20260713141742-763625a20721 or later.