CVE-2026-12624: Vault vulnerable to LIST authorization bypass via trailing-slash strip

Published Aug 10, 2026

Updated

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.

Affected Software

1 affected component

HashiCorp Vault=2.0.3, =1.21.8, =1.20.13, =1.19.19

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade HashiCorp Vault to a version that resolves this vulnerability.
Fixed in 2.0.3
Upgrade
Upgrade HashiCorp Vault to a version that resolves this vulnerability.
Fixed in 1.21.8
Upgrade
Upgrade HashiCorp Vault to a version that resolves this vulnerability.
Fixed in 1.20.13
Upgrade
Upgrade HashiCorp Vault to a version that resolves this vulnerability.
Fixed in 1.19.19
Upgrade
Upgrade HashiCorp Vault Enterprise to a version that resolves this vulnerability.
Fixed in 2.0.3

Event History

Aug 10, 2026

CVE Published

via MITRE·05:00 PM

Data Sourced

via MITRE·05:00 PM

DescriptionSeverityWeakness

Frequently Asked Questions

What is the severity of CVE-2026-12624?

The severity of CVE-2026-12624 is rated as medium with a score of 4.3.

How do I fix CVE-2026-12624?

To fix CVE-2026-12624, update HashiCorp Vault to the latest version where the vulnerability has been addressed.

What is the impact of CVE-2026-12624?

CVE-2026-12624 may allow unauthorized enumerations of entries beneath a denied path due to a bypass in LIST authorization.

What software is affected by CVE-2026-12624?

CVE-2026-12624 affects HashiCorp Vault.

When was CVE-2026-12624 published?

CVE-2026-12624 was published on August 10, 2026.