Answer in brief
CVE-2026-12624 records a Unknown severity vulnerability in Vault vulnerable to LIST authorization bypass via trailing-slash strip. The current sources do not mark it as known exploited. The current feed maps HashiCorp/Vault (generic), HashiCorp/Vault (generic), HashiCorp/Vault Enterprise (generic), HashiCorp/Vault Enterprise (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps HashiCorp/Vault (generic), HashiCorp/Vault (generic), HashiCorp/Vault Enterprise (generic), HashiCorp/Vault Enterprise (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| HashiCorp/Vaultgeneric | >=2.0.0 <2.0.3 | 2.0.3 |
| HashiCorp/Vaultgeneric | >=0 <2.0.3 | 2.0.3 |
| HashiCorp/Vault Enterprisegeneric | >=2.0.0 <2.0.3 | 2.0.3 |
| HashiCorp/Vault Enterprisegeneric | >=0 <2.0.3 | 2.0.3 |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
No valid source references are reported in the current record.
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-12624 records a Unknown severity vulnerability in Vault vulnerable to LIST authorization bypass via trailing-slash strip. The current sources do not mark it as known exploited. The current feed maps HashiCorp/Vault (generic), HashiCorp/Vault (generic), HashiCorp/Vault Enterprise (generic), HashiCorp/Vault Enterprise (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps HashiCorp/Vault (generic), HashiCorp/Vault (generic), HashiCorp/Vault Enterprise (generic), HashiCorp/Vault Enterprise (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| HashiCorp/Vaultgeneric | >=2.0.0 <2.0.3 | 2.0.3 |
| HashiCorp/Vaultgeneric | >=0 <2.0.3 | 2.0.3 |
| HashiCorp/Vault Enterprisegeneric | >=2.0.0 <2.0.3 | 2.0.3 |
| HashiCorp/Vault Enterprisegeneric | >=0 <2.0.3 | 2.0.3 |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
No valid source references are reported in the current record.
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.
Quoted source text, attributed separately from HOL analysis.