Skip to main content
VulnerabilityPublished Updated

CVE-2026-3605: HashiCorp Vault · Authentication Bypass Using an Alternate Path or Channel

Affects HashiCorp VaultSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 2.0.0 soon.

Data as of 30 Oct 2026, 11:52 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Apr 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 30 Oct 2026.

What to do

Upgrade Vault and Vault Enterprise to 2.0.0; Vault Enterprise to 1.19.16.

Affected software

ProductAffectedFixed in
HashiCorpVaultAffected
  • >=0.10.0 <2.0.0
Fixed in
  • 2.0.0
HashiCorpVault EnterpriseAffected
  • >=0.10.0 <1.19.16
Fixed in
  • 2.0.0
GitHubVaultpkg:github/VaultOther threatsAffected
  • >=0.10.0 <2.0.0
Fixed in
  • 2.0.0
GitHubVault Enterprisepkg:github/Vault EnterpriseOther threatsAffected
  • >=0.10.0 <1.19.16
Fixed in
  • 1.19.16

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.0 and Vault Enterprise 2.0.0, 1.21.5, 1.20.10, and 1.19.16. Users should upgrade to one of these fixed versions to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.

Description

An authenticated user with access to a kvv2 path through a policy containing a glob may be able to delete secrets they were not authorized to read or write, resulting in denial-of-service. This vulnerability did not allow a malicious user to delete secrets across namespaces, nor read any secret data. Fxed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0, 1.21.5, 1.20.10, and 1.19.16.

References

Community reviews

Loading reviews…