
Cloud Vulnerability DB
A community-led vulnerabilities database
CVE-2026-93335 is an authorization bypass vulnerability in HashiCorp Vault Community Edition and Vault Enterprise caused by inconsistent application of explicit ACL policy deny rules to request paths that differ only by a trailing slash. An authenticated user holding broader delete permissions on system configuration paths may bypass more specific deny rules to disable secrets engines, auth methods, or audit devices. The vulnerability affects Vault Community Edition and Vault Enterprise from version 0.2.0 up to (but not including) 2.2.2, and was published on November 13, 2026. It carries a CVSS v3.1 base score of 6.5 (Medium/Moderate) (GitHub Advisory, HashiCorp Advisory).
The root cause is classified as CWE-647 (Use of Non-Canonical URL Paths for Authorization Decisions), where Vault's ACL enforcement logic does not normalize request paths before evaluating deny rules. Specifically, when a policy includes an explicit deny rule for a path such as sys/mounts/secret, a request to sys/mounts/secret/ (with a trailing slash) may not match the deny rule and instead fall through to a broader delete permission. Exploitation requires the attacker to be authenticated and hold a broader delete permission on system configuration paths — no unauthenticated access vector exists. No public proof-of-concept code has been identified (GitHub Advisory, HashiCorp Advisory).
Successful exploitation allows an authenticated, high-privilege user to bypass intended ACL deny rules and disable or delete secrets engines, auth methods, or audit devices that were specifically protected by those rules. This can result in high integrity and availability impact — critical secrets management infrastructure could be disrupted, audit logging could be silenced, or authentication mechanisms could be disabled. Confidentiality is not directly impacted by this vulnerability, but disabling audit devices could facilitate subsequent undetected attacks (GitHub Advisory, HashiCorp Advisory).
There is no evidence of active in-the-wild exploitation or publicly available proof-of-concept code as of the disclosure date. The EPSS score is 0.0, indicating very low current probability of exploitation. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires an authenticated user with high-level administrative privileges, significantly limiting the attack surface (GitHub Advisory, HashiCorp Advisory).
delete capabilities on sys/ paths.deny rule (e.g., sys/mounts/protected-engine).DELETE /v1/sys/mounts/protected-engine/) instead of the canonical path (/v1/sys/mounts/protected-engine).sys/mounts/, sys/auth/, or sys/audit/ paths with a trailing slash (e.g., /v1/sys/mounts/engine-name/) from a token that should have been denied by policy./v1/sys/mounts/*, /v1/sys/auth/*, /v1/sys/audit/*) with trailing slashes in the path, observable in web proxy or load balancer logs.HashiCorp has released patches addressing this vulnerability: upgrade to Vault Community Edition 2.2.2 or Vault Enterprise 2.2.2, 1.21.14, or 1.19.25. As a temporary workaround prior to patching, administrators should review ACL policies and add explicit deny rules for both the canonical path and the trailing-slash variant (e.g., deny both sys/mounts/secret and sys/mounts/secret/). Additionally, monitoring Vault audit logs for unexpected modifications to secrets engines, auth methods, and audit devices is recommended until patches are applied (HashiCorp Advisory, GitHub Advisory).
The vulnerability was disclosed by HashiCorp via their security advisory forum (HCSEC-2026-56) on November 13, 2026, with patches released simultaneously. No notable independent researcher commentary or significant social media discussion has been identified beyond standard vulnerability aggregator coverage (HashiCorp Advisory).
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."