How severe is CVE-2026-63132?

CVE-2026-63132 has a CVSS 4.0 base score of 9.2, rated critical severity.

Is CVE-2026-63132 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (41st percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-63132?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2026-63132 published?

CVE-2026-63132 was published on 2026-09-23 and last updated on 2026-09-29.

CVE-2026-63132

CVE-2026-63132 is a critical-severity vulnerability with a CVSS 4.0 base score of 9.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-208.

Key facts

Severity: Critical (CVSS 4.0 base score 9.2)
EPSS exploit prediction: 0% (41st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-208
Published: 2026-09-23
Last modified: 2026-09-29

Description

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.

Frequently asked questions

What is CVE-2026-63132?: 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.
How severe is CVE-2026-63132?: CVE-2026-63132 has a CVSS 4.0 base score of 9.2, rated critical severity.
Is CVE-2026-63132 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (41st percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-63132?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2026-63132 published?: CVE-2026-63132 was published on 2026-09-23 and last updated on 2026-09-29.

References

Other CWE-208 vulnerabilities

CVE-2026-77987 — Critical (CVSS 9.8): A server-side request forgery (SSRF) vulnerability was identified in the notebook viewer of GitHub Enterprise Server.…
CVE-2023-41313 — Critical (CVSS 9.8): The authentication method in Apache Doris versions before 2.0.0 was vulnerable to timing attacks. Users are recommended…
CVE-2026-16315 — High (CVSS 8.7): OMICRON StationGuard before version 4.10 contains a cryptographic timing side-channel vulnerability in the backend…
CVE-2024-42512 — High (CVSS 8.6): Vulnerability in the OPC UA .NET Standard Stack before 1.5.374.158 allows an unauthorized attacker to bypass…
CVE-2026-43606 — High (CVSS 8.5): Observable Timing Discrepancy in the AMD Vitis Libraries ECDSA secp256k1 component could allow attackers with local…
CVE-2025-53940 — High (CVSS 8.5): Quiet is an alternative to team chat apps like Slack, Discord, and Element that does not require trusting a central…

Browse all CWE-208 vulnerabilities →