CVE
HashiCorp Vault ACL deny bypass via trailing slash in request paths
- Exploited
- No known exploitation
- Fix
- Fixed in Vault 2.2.2 · Vault Enterprise 2.2.2, 1.19.25, 1.21.14
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: Vault 2.2.2 · Vault Enterprise 2.2.2, 1.19.25, 1.21.14.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.30% · 23rd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Vault Community Edition and Vault Enterprise can let a user with high privileges bypass explicit ACL deny rules by changing a request path only by a trailing slash, which could let them disable a secrets engine, auth method, or audit device that a more specific deny rule was meant to protect. The attack can be carried out remotely over the network, but it requires the attacker to already be logged in with high privileges.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Vault Community Edition and Vault Enterprise did not consistently apply explicit ACL policy deny rules to request paths that differ only by a trailing slash. This may allow an authenticated user who holds a broader delete permission on system configuration paths to disable a secrets engine, auth method, or audit device that a more specific deny rule was intended to protect. This vulnerability (CVE-2026-93335) is fixed in Vault Community Edition 2.2.2 and Vault Enterprise 2.2.2, 1.21.14, and 1.19.25.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: Vault 2.2.2 · Vault Enterprise 2.2.2, 1.19.25, 1.21.14.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-93335 (Vault vulnerable to ACL deny bypass via trailing slash), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-93335 (entry last updated 2026-11-13):
Affected:
- HashiCorp Vault: from 0.2.0, fixed in 2.2.2
- HashiCorp Vault Enterprise: from 0.2.0, fixed in 1.19.25; from 1.20.0, fixed in 1.21.14; from 2.0.0, fixed in 2.2.2
Fixed versions: 2.2.2, 1.19.25, 1.21.14.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-93335 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-93335 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://discuss.hashicorp.com/t/hcsec-2026-56-vault-vulnerable-to-acl-deny-bypass-via-trailing-slash/78199
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-93335
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-93335"}.Timeline
- CVE published
- First seen by cve.now1 day
- Record last updated
Affected versions
- HashiCorp Vault
From 0.2.0 · fixed in 2.2.2
- HashiCorp Vault Enterprise
From 0.2.0 · fixed in 1.19.25; From 1.20.0 · fixed in 1.21.14; From 2.0.0 · fixed in 2.2.2
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-93335
Is CVE-2026-93335 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-93335?
Vault: from 0.2.0 before 2.2.2. Vault Enterprise: from 0.2.0 before 1.19.25; from 1.20.0 before 1.21.14; from 2.0.0 before 2.2.2.Source: cve.now feed data
How do I fix CVE-2026-93335?
Upgrade to a fixed version: Vault 2.2.2 · Vault Enterprise 2.2.2, 1.19.25, 1.21.14.Source: cve.now feed data