CVE-2026-63132

CRITICALPre-NVD 9.29.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (50th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-85520 (ENISA EUVD) · GHSA-34fc-gh42-pj53 (GitHub Security Advisories)Source: ENISA EUVD

9.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.2
EG Score
9.2CRITICALmedium confidence
EG Risk
42
EG Risk 42/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity92% × 45%
Impact severity (EG Severity): CVSS 9.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
50th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.2): severity, escalated by confirmed exploitation. This CVE's 9.2 is its impact severity (EG Severity), not escalated.

EG Severity
9.2 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 22, 2026

Last Modified

September 29, 2026

Advisory Details (6)

Auto-updated Sep 23, 2026
Patch available. Sources: github, github_pr, github_commit.
Web page

vault/CHANGELOG.md at main · hashicorp/vault · GitHub

https://github.com/hashicorp/vault/blob/main/CHANGELOG.md#203
GitHub commit

commit 763625a20721 (openbao/openbao)

Fix landed in openbao/openbao commit 763625a20721 — awaiting tagged release

https://github.com/openbao/openbao/commit/763625a2072103ea9e9122f2a8408e0b988d287a
GitHub commit

commit 0f2d90c331f2 (openbao/openbao)

Fix landed in openbao/openbao commit 0f2d90c331f2 — awaiting tagged release

https://github.com/openbao/openbao/commit/0f2d90c331f25d1c6cd108638da03f4c7bd949a8
GitHub pull request

Switch to constant-time comparison recovery token (#3388)

Fix merged in openbao/openbao PR #3472 on 2026-07-13 — awaiting tagged release

https://github.com/openbao/openbao/pull/3472
GitHub pull request

Switch to constant-time comparison recovery token

Fix merged in openbao/openbao PR #3388 on 2026-07-13 — awaiting tagged release

https://github.com/openbao/openbao/pull/3388
GitHub advisoryMentions a patch (unverified)

OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack · Advisory · openbao/openbao · GitHub

https://github.com/openbao/openbao/security/advisories/GHSA-34fc-gh42-pj53

Vendor Advisories for CVE-2026-63132(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/openbao/openbao @ 0.0.0-20260713141742-763625a20721 (fixes < 0.0.0-20260713141742-763625a20721)—ghsa
gogithub.com/openbao/openbao—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/openbao/openbao—
  • every version up to 0.0.0-20260713141742-763625a20721: fixed in 0.0.0-20260713141742-763625a20721
  • 0.1.0 through 1.1.5: no fix on record
  • 0.1.0 on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 67× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-02 07:34 UTCEG score recompute
  2. 2026-11-02 07:34 UTCGHSA enrichmentGHSA-34fc-gh42-pj53 · GitHub severity CRITICAL
  3. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  4. 2026-11-01 07:51 UTCGHSA enrichmentGHSA-34fc-gh42-pj53 · GitHub severity CRITICAL
  5. 2026-11-01 07:41 UTCEG score recompute
  6. 2026-11-01 07:41 UTCGHSA enrichmentGHSA-34fc-gh42-pj53 · GitHub severity CRITICAL
  7. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  8. 2026-10-31 08:07 UTCEG score recompute
  9. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  10. 2026-10-30 08:22 UTCEG score recompute
  11. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  12. 2026-10-29 08:39 UTCEG score recompute
  13. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  14. 2026-10-28 08:54 UTCEG score recompute
  15. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  16. 2026-10-27 08:37 UTCEG score recompute
  17. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  18. 2026-10-26 06:52 UTCEG score recompute
  19. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  20. 2026-10-25 14:13 UTCEG score recompute
  21. 2026-10-25 07:04 UTCEG score recompute
  22. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  23. 2026-10-24 07:19 UTCEG score recompute
  24. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-10-23 07:35 UTCEG score recompute
Show 61 more
  1. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-10-22 07:49 UTCEG score recompute
  3. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-10-21 08:05 UTCEG score recompute
  5. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-20 08:21 UTCEG score recompute
  7. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-10-19 08:35 UTCEG score recompute
  9. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-18 03:23 UTCEG score recompute
  11. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-10-17 07:02 UTCEG score recompute
  13. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  14. 2026-10-16 07:17 UTCEG score recompute
  15. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-10-15 06:13 UTCEG score recompute
  17. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  18. 2026-10-14 01:49 UTCEG score recompute
  19. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-10-12 22:02 UTCEG score recompute
  21. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-10-12 15:49 UTCEG score recompute
  23. 2026-10-11 19:33 UTCEG score recompute
  24. 2026-10-11 16:48 UTCEG score recompute
  25. 2026-10-11 14:10 UTCEG score recompute
  26. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  27. 2026-10-10 23:19 UTCEG score recompute
  28. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  29. 2026-10-09 20:26 UTCEG score recompute
  30. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  31. 2026-10-08 21:03 UTCEG score recompute
  32. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  33. 2026-10-08 01:45 UTCEG score recompute
  34. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  35. 2026-10-06 18:48 UTCEG score recompute
  36. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  37. 2026-10-05 20:03 UTCEG score recompute
  38. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  39. 2026-10-05 01:05 UTCEG score recompute
  40. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  41. 2026-10-03 14:40 UTCEG score recompute
  42. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  43. 2026-10-02 19:27 UTCEG score recompute
  44. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  45. 2026-10-02 00:04 UTCEG score recompute
  46. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  47. 2026-09-30 16:46 UTCEG score recompute
  48. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  49. 2026-09-29 18:34 UTCEG score recompute
  50. 2026-09-28 23:25 UTCEG score recompute
  51. 2026-09-28 15:35 UTCEG score recompute
  52. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  53. 2026-09-27 16:41 UTCEG score recompute
  54. 2026-09-26 17:51 UTCEG score recompute
  55. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  56. 2026-09-26 02:02 UTCEG score recompute
  57. 2026-09-24 15:22 UTCEG score recompute
  58. 2026-09-23 19:18 UTCEG score recompute
  59. 2026-09-23 18:22 UTCEG score recomputeFirst assessed: 9.2 CRITICAL
  60. 2026-09-23 18:21 UTCMITRE cvelistV5CVSS v3 → 9.2 · CVSS v4 → 9.2
  61. 2026-09-22 20:45 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-63132?
CVE-2026-63132 is a critical-severity vulnerability; its CVE record was published on September 22, 2026. 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…
When was the CVE record for CVE-2026-63132 published?
The CVE record for CVE-2026-63132 was published on September 22, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 29, 2026; the record at its source may have been updated since.
Is CVE-2026-63132 actively exploited?
CVE-2026-63132 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63132?
CVE-2026-63132 has a CVSS base score of 9.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-63132?
A fix for CVE-2026-63132 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-63132 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63132

Explore →

Is Your Infrastructure Affected by CVE-2026-63132?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs