CVE-2026-63131

MEDIUMPre-NVD 6.06.0
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st 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 — 4 sources updated this week

Also known asEUVD-2026-85519 (ENISA EUVD) · GHSA-xp3c-3jw3-4vcr (GitHub Security Advisories) · GO-2026-6579 (OSV.dev)Source: ENISA EUVD

6.0EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.0Exploit: 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 vault/policy/acl.go could evaluate a broader wildcard ACL grant before more-specific trailing-wildcard ACL paths with capabilities = ["deny"] for a LIST operation. When a parent path permitted LIST and a child path was denied, the trailing-slash lookup could therefore allow listing the denied path. Other operation types are outside the repository advisory's affected scope. This issue is fixed in version 2.6.0.

CVSS v3
6.0
EG Score
6.0MEDIUMmedium confidence
EG Risk
27
EG Risk 27/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)
Severity60% × 45%
Impact severity (EG Severity): CVSS 6.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.5%
EPSS %ILE
41st
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 (6.0): severity, escalated by confirmed exploitation. This CVE's 6.0 is its impact severity (EG Severity), not escalated.

EG Severity
6.0 MEDIUMCVSS-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.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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_pr, github_commit, github.
Web page

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

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

commit f58d848c139e (openbao/openbao)

Fix landed in openbao/openbao commit f58d848c139e — awaiting tagged release

https://github.com/openbao/openbao/commit/f58d848c139e5ba71aa63103fcfe101972b999fc
GitHub commit

commit 2e9625d6cebe (openbao/openbao)

Fix landed in openbao/openbao commit 2e9625d6cebe — awaiting tagged release

https://github.com/openbao/openbao/commit/2e9625d6cebe4639d051ef53dd6ce7c49914ae6a
GitHub pull request

Fix LIST ACL deny bypass caused by wildcards (#3389)

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

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

Fix LIST ACL deny bypass caused by wildcards

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

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

OpenBao Skips Stricter Deny Policy for LIST operations · Advisory · openbao/openbao · GitHub

https://github.com/openbao/openbao/security/advisories/GHSA-xp3c-3jw3-4vcr

Vendor Advisories for CVE-2026-63131(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-20260713133043-f58d848c139e (fixes < 0.0.0-20260713133043-f58d848c139e)—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-20260713133043-f58d848c139e: fixed in 0.0.0-20260713133043-f58d848c139e
  • 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 10× in last 7d / 47× 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-01 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-11-01 07:41 UTCGHSA enrichmentGHSA-xp3c-3jw3-4vcr · GitHub severity MODERATE
  3. 2026-11-01 07:41 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-30 08:55 UTCOSV refresh
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-10-25 14:13 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  15. 2026-10-22 19:51 UTCEG score recompute
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  21. 2026-10-18 03:23 UTCEG score recompute
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  23. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
Show 40 more
  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  3. 2026-10-12 15:49 UTCEG score recompute
  4. 2026-10-11 19:33 UTCEG score recompute
  5. 2026-10-11 16:48 UTCEG score recompute
  6. 2026-10-11 14:10 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  9. 2026-10-10 15:42 UTCEG score recompute
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  11. 2026-10-09 16:19 UTCEG score recompute
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  13. 2026-10-08 17:11 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  15. 2026-10-07 13:42 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  17. 2026-10-06 14:33 UTCEG score recompute
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  19. 2026-10-05 15:22 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  21. 2026-10-03 16:40 UTCEG score recompute
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  23. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  24. 2026-10-02 17:32 UTCEG score recompute
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  26. 2026-09-30 18:48 UTCEG score recompute
  27. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  28. 2026-09-29 19:23 UTCEG score recompute
  29. 2026-09-29 11:26 UTCEG score recompute
  30. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  31. 2026-09-28 12:18 UTCEG score recompute
  32. 2026-09-27 13:10 UTCEG score recompute
  33. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  34. 2026-09-26 14:02 UTCEG score recompute
  35. 2026-09-24 15:30 UTCEG score recompute
  36. 2026-09-24 14:51 UTCEG score recompute
  37. 2026-09-23 19:18 UTCEG score recompute
  38. 2026-09-23 18:22 UTCEG score recomputeFirst assessed: 6.0 MEDIUM
  39. 2026-09-23 18:21 UTCMITRE cvelistV5CVSS v3 → 6 · CVSS v4 → 6
  40. 2026-09-22 20:45 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-63131?
CVE-2026-63131 is a medium-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 vault/policy/acl.go could evaluate a broader wildcard ACL grant before more-specific trailing-wildcard ACL paths with capabilities = ["deny"] for a LIST operation. When a parent path permitted LIST and a…
When was the CVE record for CVE-2026-63131 published?
The CVE record for CVE-2026-63131 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-63131 actively exploited?
CVE-2026-63131 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63131?
CVE-2026-63131 has a CVSS base score of 6.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-63131?
A fix for CVE-2026-63131 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-63131 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-63131

Explore →

Is Your Infrastructure Affected by CVE-2026-63131?

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

Book a Demo →Browse All CVEs