Vault: Authentication Bypass Using an Alternate Path or Channel
CVE-2026-3605 is a high-severity authentication bypass using an alternate path or channel vulnerability in Vault from HashiCorp, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 2.0.0 as the first without the flaw, so updating Vault to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.38% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Vault to 2.0.0 or a later version.
- Update Vault Enterprise to 2.0.0 or a later version.
- Read the advisory on discuss.hashicorp.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| HashiCorp | Vault | 0.10.0 up to, but not including, 2.0.0 | 2.0.0 |
| HashiCorp | Vault Enterprise | 0.10.0 up to, but not including, 2.0.0 | 2.0.0 |
| Red Hat | Red Hat OpenShift Container Platform 4 | Not specified in the record | Not stated |
| Red Hat | Red Hat Openshift Data Foundation 4 | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H. Scored by CNA (hashicorp.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.1 | High | CNA (hashicorp.com) |
| CVSS 3.1 | 8.1 | High | CNA |
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Authentication Bypass Using an Alternate Path or Channel
The product requires authentication, but the product has an alternate path or channel that does not require authentication.
How developers prevent this class of flaw
- Funnel all access through a single choke point to simplify how users can access a resource. For every access, perform a check to determine if the user has permissions to access the resource.
More Authentication Bypass Using an Alternate Path or Channel vulnerabilities (CWE-288)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in Vault
- 7.2 High severity
- 8.0 High severity
- 7.5 High severity
- 8.6 High severity
- 8.8 High severity
- 7.5 High severity
Recent Authentication Bypass Using an Alternate Path or Channel vulnerabilities
- 8.2 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 8.1 High severity
- 7.5 High severity
- 9.8 Critical severity
Spotted an error? Tell us.