Skip to main content
VulnerabilityPublished

CVE-2026-12624: HashiCorp Vault · Incorrect Authorization

Affects HashiCorp VaultSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 2.0.3 when convenient.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.3, 1.21.8
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Upgrade Vault and Vault Enterprise to 2.0.3; Vault Enterprise to 1.21.8.

Affected software

ProductAffectedFixed in
HashiCorpVaultAffected
  • <2.0.3
Fixed in
  • 2.0.3
HashiCorpVault EnterpriseAffected
  • <1.21.8
Fixed in
  • 2.0.3
GitHubVaultpkg:github/VaultOther threatsAffected
  • <2.0.3
Fixed in
  • 2.0.3
GitHubVault Enterprisepkg:github/Vault EnterpriseOther threatsAffected
  • <1.21.8
Fixed in
  • 1.21.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

Description

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.

References

Community reviews

Loading reviews…