CVE-2026-3605: CWE-288: Authentication Bypass Using an Alternate Path or Channel in HashiCorp Vault
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.
AI Analysis
Technical Summary
This vulnerability (CVE-2026-3605) involves an authentication bypass using an alternate path or channel (CWE-288) in HashiCorp Vault. Specifically, an authenticated user with a policy granting access to a kvv2 path through a glob pattern can delete secrets beyond their intended permissions, resulting in denial-of-service. The vulnerability does not permit unauthorized reading of secret data or deletion of secrets across namespaces. The issue is addressed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0, 1.21.5, 1.20.10, and 1.19.16. The CVSS v3.1 score is 8.1 (High), reflecting network attack vector, low attack complexity, low privileges required, no user interaction, unchanged scope, no confidentiality impact, high integrity impact, and high availability impact. No known exploits are reported in the wild. The vendor advisory from Red Hat confirms the fix availability.
Potential Impact
An attacker who is authenticated and has access to a kvv2 path via a glob-based policy can delete secrets they are not authorized to manage, causing denial-of-service. There is no impact on confidentiality as secrets cannot be read without authorization, and secrets in other namespaces cannot be deleted. The integrity and availability of affected secrets are compromised within the scope of the user's namespace and policy.
Mitigation Recommendations
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.
CVE-2026-3605: CWE-288: Authentication Bypass Using an Alternate Path or Channel in HashiCorp Vault
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.
CVSS v3.1
Score 8.1high
Affected software
pkg:github/hashicorp/vaultRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CVE-2026-3605) involves an authentication bypass using an alternate path or channel (CWE-288) in HashiCorp Vault. Specifically, an authenticated user with a policy granting access to a kvv2 path through a glob pattern can delete secrets beyond their intended permissions, resulting in denial-of-service. The vulnerability does not permit unauthorized reading of secret data or deletion of secrets across namespaces. The issue is addressed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0, 1.21.5, 1.20.10, and 1.19.16. The CVSS v3.1 score is 8.1 (High), reflecting network attack vector, low attack complexity, low privileges required, no user interaction, unchanged scope, no confidentiality impact, high integrity impact, and high availability impact. No known exploits are reported in the wild. The vendor advisory from Red Hat confirms the fix availability.
Potential Impact
An attacker who is authenticated and has access to a kvv2 path via a glob-based policy can delete secrets they are not authorized to manage, causing denial-of-service. There is no impact on confidentiality as secrets cannot be read without authorization, and secrets in other namespaces cannot be deleted. The integrity and availability of affected secrets are compromised within the scope of the user's namespace and policy.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- HashiCorp
- Date Reserved
- 2026-03-05T16:37:23.520Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
- Epss Score
- 0.00014
- Epss Percentile
- 0.02759
- Epss Date
- 2026-04-26
- Gcve Source
- db.gcve.eu
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-3605","vendor":"Red Hat"}]
Threat ID: 69e2142082d89c981fcd7c21
Added to database: 04/17/2026, 11:06:08 UTC
Last enriched: 07/15/2026, 09:08:58 UTC
Last updated: 07/31/2026, 19:22:58 UTC
Views: 103
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.
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.