CVE-2026-12624: CWE-863: Incorrect Authorization in HashiCorp Vault
CVE-2026-12624 is an authorization vulnerability in HashiCorp Vault's ACL policy engine where a wildcard deny rule was not consistently enforced against LIST requests with a trailing slash. This flaw could allow tokens with broader allow permissions alongside narrower wildcard deny rules to enumerate entries under paths they should be denied access to. The issue is fixed in Vault Community Edition 2.0.3 and Vault Enterprise versions 2.0.3, 1.21.8, 1.20.13, and 1.19.19. The vulnerability has a medium severity with a CVSS score of 4.3.
AI Analysis
Technical Summary
HashiCorp Vault's ACL policy engine failed to consistently enforce wildcard deny rules on LIST requests that include a trailing slash on the denied path. This inconsistency allows a token that has a broader allow rule combined with a narrower wildcard deny rule to enumerate the names of entries beneath a path that should be denied. This is an incorrect authorization vulnerability categorized under CWE-863. The vulnerability is addressed in Vault Community Edition 2.0.3 and Vault Enterprise 2.0.3, 1.21.8, 1.20.13, and 1.19.19.
Potential Impact
An attacker or user holding a token with a broader allow rule alongside a narrower wildcard deny rule could enumerate entries under paths they are supposed to be denied access to. This could lead to information disclosure of path names within Vault, potentially aiding further attacks or reconnaissance. There is no impact on integrity or availability reported.
Mitigation Recommendations
This vulnerability 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. Users should upgrade to these versions or later to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.
CVE-2026-12624: CWE-863: Incorrect Authorization in HashiCorp Vault
Description
CVE-2026-12624 is an authorization vulnerability in HashiCorp Vault's ACL policy engine where a wildcard deny rule was not consistently enforced against LIST requests with a trailing slash. This flaw could allow tokens with broader allow permissions alongside narrower wildcard deny rules to enumerate entries under paths they should be denied access to. The issue is fixed in Vault Community Edition 2.0.3 and Vault Enterprise versions 2.0.3, 1.21.8, 1.20.13, and 1.19.19. The vulnerability has a medium severity with a CVSS score of 4.3.
CVSS v3.1
Score 4.3medium
Affected software
pkg:github/Vault EnterpriseRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
HashiCorp Vault's ACL policy engine failed to consistently enforce wildcard deny rules on LIST requests that include a trailing slash on the denied path. This inconsistency allows a token that has a broader allow rule combined with a narrower wildcard deny rule to enumerate the names of entries beneath a path that should be denied. This is an incorrect authorization vulnerability categorized under CWE-863. The vulnerability is addressed in Vault Community Edition 2.0.3 and Vault Enterprise 2.0.3, 1.21.8, 1.20.13, and 1.19.19.
Potential Impact
An attacker or user holding a token with a broader allow rule alongside a narrower wildcard deny rule could enumerate entries under paths they are supposed to be denied access to. This could lead to information disclosure of path names within Vault, potentially aiding further attacks or reconnaissance. There is no impact on integrity or availability reported.
Mitigation Recommendations
This vulnerability 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. Users should upgrade to these versions or later to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- HashiCorp
- Date Reserved
- 2026-06-18T14:22:11.863Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7a0655bf8831d53936fe2a
Added to database: 08/10/2026, 17:11:49 UTC
Last enriched: 08/10/2026, 19:31:24 UTC
Last updated: 08/10/2026, 19:31:24 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.