Security Bulletin
Summary
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.
Vulnerability Details
CVEID: CVE-2026-93335
DESCRIPTION: Vault matched exact-path and segment-wildcard (+) ACL rules against the request path as supplied, so a rule written for a path did not apply to the same path with a trailing slash added or removed. The system endpoints that disable secrets engines, auth methods, and audit devices treat both forms as the same resource. As a result, a request using the other form could fail to match an explicit deny rule, be authorized by a broader matching grant, and still disable the protected resource. Other operations on these paths, such as reading a secrets engine's configuration, were similarly affected. In Vault Enterprise, Sentinel endpoint governing policies attached to exact paths were also not applied to the other form. Disabling a secrets engine removes its stored data and revokes its leases, disabling an auth method revokes the tokens issued through it, and disabling an audit device may reduce audit coverage. This issue requires an authenticated user whose policies grant delete on the broader path, and disabling auth methods and audit devices also requires the sudo capability. Deployments whose policies do not combine a broader grant with a more specific explicit deny rule on these paths are not affected.
CWE: CWE-647: Non-Canonical URL Authorization
CVSS Source: HashiCorp Inc.
CVSS Base score: 6.5
CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H)
Affected Products and Versions
| Affected Product(s) | Version(s) |
| Vault Community Edition | affected from 0.2.0 up to 2.2.2 |
| Vault Enterprise | affected from 0.2.0 up to 2.2.2, unaffected from 1.19.25, 1.21.14 |
Remediation/Fixes
Customers should evaluate the risk associated with this issue and consider upgrading to Vault Community Edition 2.2.2 or Vault Enterprise 2.2.2, 1.21.14, or 1.19.25. After upgrading, an exact-path rule defined for only one form of a path, with or without a trailing slash, also applies to the other form, so operators should review policies that rely on the two forms being governed by different rules.
Get Notified about Future Security Bulletins
References
Acknowledgement
This issue was reported to HashiCorp by Tal Vaknin and other internal and external parties.
Change History
12 Nov 2026: Initial Publication
*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.
Disclaimer
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES ""AS IS"" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. In addition to other efforts to address potential vulnerabilities, IBM periodically updates the record of components contained in our product offerings. As part of that effort, if IBM identifies previously unidentified packages in a product/service inventory, we address relevant vulnerabilities regardless of CVE date. Inclusion of an older CVEID does not demonstrate that the referenced product has been used by IBM since that date, nor that IBM was aware of a vulnerability as of that date. We are making clients aware of relevant vulnerabilities as we become aware of them. "Affected Products and Versions" referenced in IBM Security Bulletins are intended to be only products and versions that are supported by IBM and have not passed their end-of-support or warranty date. Thus, failure to reference unsupported or extended-support products and versions in this Security Bulletin does not constitute a determination by IBM that they are unaffected by the vulnerability. Reference to one or more unsupported versions in this Security Bulletin shall not create an obligation for IBM to provide fixes for any unsupported or extended-support products or versions.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
12 November 2026
Initial Publish date:
12 November 2026
UID
ibm17296635