CVE-2026-631329.2CriticalCWE-208

CVE-2026-63132: OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack

openbao

Affected: openbao · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.6%probability of exploitation in the next 30 days

50th percentile

050100

Higher than 50% of scored CVEs

9.2CriticalCVSS 4.0

LowMediumHighCrit.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

openbao · openbao< 2.6.0

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Observable Timing Discrepancy · Information Disclosure
Vendor: openbao
Published: September 2026
Band: Unlikely (under 1%), September 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-63132 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.