CVE-2026-3605: HashiCorp Vault · Authentication Bypass Using an Alternate Path or Channel
Affects HashiCorp VaultSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 2.0.0 soon.
Data as of 30 Oct 2026, 11:52 UTC
- 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:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| HashiCorpVault | Affected
| Fixed in
|
| HashiCorpVault Enterprise | Affected
| Fixed in
|
GitHubVaultpkg:github/VaultOther threats | Affected
| Fixed in
|
GitHubVault Enterprisepkg:github/Vault EnterpriseOther threats | Affected
| Fixed in
|
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
- discuss.hashicorp.com/t/hcsec-2026-05-vault-kvv2-metadata-and-secret-deletion-policy-bypass-denial-of-service/77342 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-3605 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2459105 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-3605.json (opens in a new tab)