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.
CVE-2026-63131
This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.0
- EG Score
- 6.0(low)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity60% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 22, 2026
Last Modified
September 23, 2026
Advisory Details (6)
Auto-updated Sep 23, 2026vault/CHANGELOG.md at main · hashicorp/vault · GitHub
https://github.com/hashicorp/vault/blob/main/CHANGELOG.md#203commit f58d848c139e (openbao/openbao)
Fix landed in openbao/openbao commit f58d848c139e — awaiting tagged release
https://github.com/openbao/openbao/commit/f58d848c139e5ba71aa63103fcfe101972b999fccommit 2e9625d6cebe (openbao/openbao)
Fix landed in openbao/openbao commit 2e9625d6cebe — awaiting tagged release
https://github.com/openbao/openbao/commit/2e9625d6cebe4639d051ef53dd6ce7c49914ae6aFix 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/3474Fix 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/3389OpenBao Skips Stricter Deny Policy for LIST operations · Advisory · openbao/openbao · GitHub
https://github.com/openbao/openbao/security/advisories/GHSA-xp3c-3jw3-4vcrVendor 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.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-09-23 19:18 UTCEG score recompute
- 2026-09-23 18:22 UTCEG score recompute▲ 6.00
- 2026-09-23 18:21 UTCMITRE cvelistV5CVSS v3 → 6 · CVSS v4 → 6
- 2026-09-22 20:45 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(4)
What is CVE-2026-63131?
When was CVE-2026-63131 disclosed?
What is the CVSS score of CVE-2026-63131?
How do I remediate CVE-2026-63131?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-63131
Is Your Infrastructure Affected by CVE-2026-63131?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.