{"affected":[{"defaultStatus":"unaffected","platforms":["64 bit","32 bit","x86","ARM","MacOS","Windows","Linux"],"product":"Vault","source":"CNA: HashiCorp","vendor":"HashiCorp","versions":[{"lessThan":"2.2.2","status":"affected","version":"0.2.0","versionType":"semver"}]},{"defaultStatus":"unaffected","platforms":["64 bit","32 bit","x86","ARM","MacOS","Windows","Linux"],"product":"Vault Enterprise","source":"CNA: HashiCorp","vendor":"HashiCorp","versions":[{"changes":[{"at":"1.19.25","status":"unaffected"},{"at":"1.21.14","status":"unaffected"}],"lessThan":"2.2.2","status":"affected","version":"0.2.0","versionType":"semver"}]}],"cveId":"CVE-2026-93335","cwes":["CWE-647"],"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.","epss":null,"exploits":[],"kev":null,"metrics":[{"score":6.5,"severity":"medium","source":"CNA: HashiCorp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H","version":"3.1"}],"modifiedAt":1794522734454,"publishedAt":1794522734454,"references":[{"source":"CNA: HashiCorp","tags":[],"url":"https://discuss.hashicorp.com/t/hcsec-2026-56-vault-vulnerable-to-acl-deny-bypass-via-trailing-slash/78199"}],"remediation":[],"revision":"32461a9eb691ff1fe0fd3fb1fcaf3d287a225c5d6f8b06b170eaadadb5c58ecd","sources":[{"modifiedAt":1794522734454,"name":"CNA: HashiCorp","retrievedAt":1794524947853,"url":"https://www.cve.org/CVERecord?id=CVE-2026-93335"}],"ssvc":null,"status":"published","title":"Vault vulnerable to ACL deny bypass via trailing slash","updatedAt":1794524947853}