CVE-2026-12624

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 90% of all CVEs by exploit prediction. 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Vault’s ACL policy engine did not consistently enforce a wildcard (glob) deny rule against LIST requests made with a trailing slash on the denied path. This may allow a token holding a broader allow rule alongside a narrower wildcard deny rule to enumerate the names of entries beneath a path it was intended to be denied access to. This vulnerability (CVE-2026-12624) is fixed in Vault Community Edition 2.0.3 and Vault Enterprise 2.0.3, 1.21.8, 1.20.13, and 1.19.19.

CVSS v3
4.3
EG Score
4.3(medium)
EG Risk
19(Track)
EG Risk 19/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 computed
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 11, 2026

References (1)

Vendor Advisories for CVE-2026-12624(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 12× in last 7d / 22× 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.

  1. 2026-08-19 20:18 UTCEG score recompute
  2. 2026-08-19 17:03 UTCEPSS rescore
  3. 2026-08-18 19:51 UTCEG score recompute
  4. 2026-08-18 13:48 UTCEPSS rescore
  5. 2026-08-17 19:25 UTCEG score recompute
  6. 2026-08-16 18:59 UTCEG score recompute
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 02:14 UTCEPSS rescore
  9. 2026-08-15 18:31 UTCEG score recompute
  10. 2026-08-15 01:30 UTCEPSS rescore
  11. 2026-08-14 18:05 UTCEG score recompute
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-12 17:04 UTCEG score recompute
  14. 2026-08-12 13:50 UTCEPSS rescore
  15. 2026-08-11 16:37 UTCEG score recompute
  16. 2026-08-11 16:07 UTCEG score recompute
  17. 2026-08-11 15:37 UTCEG score recompute
  18. 2026-08-11 14:33 UTCEG score recompute
  19. 2026-08-11 13:42 UTCEPSS rescore
  20. 2026-08-10 17:22 UTCEG score recompute
  21. 2026-08-10 17:10 UTCEG score recompute
  22. 2026-08-10 17:09 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-12624?
CVE-2026-12624 is a medium vulnerability published on August 10, 2026. Vault’s ACL policy engine did not consistently enforce a wildcard (glob) deny rule against LIST requests made with a trailing slash on the denied path. This may allow a token holding a broader allow rule alongside a narrower wildcard deny rule to enumerate the names of entries beneath a path it was…
When was CVE-2026-12624 disclosed?
CVE-2026-12624 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12624 actively exploited?
CVE-2026-12624 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.2% of all scored CVEs.
What is the CVSS score of CVE-2026-12624?
CVE-2026-12624 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-12624?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12624, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-12624

Explore →

Is Your Infrastructure Affected by CVE-2026-12624?

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

Start Free Scan →Browse All CVEs