Skip to content
Fencer Vulns
critical 9.2

CVE-2026-63132 json

OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack

published 2026-09-22 47 d ago modified 2026-10-01 38 d ago also BIT-openbao-2026-63132 , EUVD-2026-85520 , GHSA-34fc-gh42-pj53 , GO-2026-6553

cvss
9.2
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/openbao/openbao 0.0.0-20260713141742-763625a20721
  • bitnami openbao 2.6.0
  • openbao openbao 2.6.0
  • linuxfoundation openbao 2.6.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-63132 updated cvss 7.4

OpenBao: OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack

  • Red Hat Hardened Images opentofu1.11
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift GitOps openshift-gitops-1/dex-rhel9
    affected: no fix available
  • Red Hat Cryostat 4 cryostat/cryostat-storage-rhel9
    not affected: component not present
  • Red Hat Hardened Images dex, opentofu1.10, opentofu1.12
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
46 d ago

Exploit prediction

0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 4.0 9.2 CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA 4.0 9.2 CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
go github.com/openbao/openbao
<0.0.0-20260713141742-763625a20721
>=0.1.0, <=1.1.5
>=0.1.0
0.0.0-20260713141742-763625a20721
bitnami openbao
<2.6.0
2.6.0

Affected products

  • openbao openbao

Classification

Weakness
  • CWE-208 Observable Timing Discrepancy

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.