Security Bulletin
Summary
Vault and Vault Enterprise did not consistently evaluate ACL policies against the canonical form of resource and policy names. This may allow an authenticated user with delegated permissions to bypass an explicit deny restriction and access a protected resource or assign a denied policy, potentially leading to privilege escalation. This vulnerability (CVE-2026-89322) is fixed in Vault Community Edition 2.1.2, and Vault Enterprise 2.1.2, 1.21.12, 1.20.17, and 1.19.23.
Vulnerability Details
CVEID: CVE-2026-89322
DESCRIPTION: Vault evaluated ACL policies against resource and policy names as supplied in a request, while the receiving component later normalized those names into their canonical form, for example by disregarding letter case or surrounding whitespace. A request that referred to a protected resource or policy using a non-canonical name could therefore avoid a restriction during policy evaluation and still be applied to the protected resource or denied policy. This may allow a delegated user to access or modify a resource protected by a more specific rule, such as obtaining credentials for an explicitly denied auth method role, or to assign an explicitly denied policy to a token, role, user, or identity. In Vault Enterprise, Sentinel policies evaluated against the request path were similarly affected. Exploitation requires an authenticated principal holding broad delegated permissions on an affected endpoint, and a policy that relies either on a more specific rule to deny or limit access alongside a broader allow rule, or on value-specific denied_parameters to restrict assignable policy names. Assigning a denied policy also requires that the policy already exists and that the principal can obtain a token carrying it. Root and internal policies cannot be assigned through this issue, and token creation without sudo remains limited to the caller's own policies. Deployments that do not combine broad allow rules with more specific restrictions on these resources, do not use non-canonical casing in policy names, and do not use denied_parameters to restrict policy names, are not affected.
CWE: CWE-178: Improper Handling of Case Sensitivity
CVSS Source: HashiCorp Inc.
CVSS Base score: 7.2
CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H)
Affected Products and Versions
| Affected Product(s) | Version(s) |
| Vault Community Edition | affected from 0.0.1 up to 2.1.2 |
| Vault Enterprise | affected from 0.0.1 up to 2.1.2, unaffected from 1.21.12, 1.20.17, 1.19.23 |
Remediation/Fixes
Customers should evaluate the risk associated with this issue and consider upgrading to Vault Community Edition 2.1.2, or Vault Enterprise 2.1.2, 1.21.12, 1.20.17, or 1.19.23. After upgrading, ACL policy rules and Vault Enterprise Sentinel policies for affected resources are evaluated against the lowercase resource name, so existing rules that reference mixed-case resource names, including deny rules, will no longer match and should be rewritten in lowercase before upgrading. The Okta, LDAP, and RADIUS auth methods, and Vault Enterprise SCIM clients, are not covered by this fix; operators should avoid combining broad allow rules with more specific deny rules on those resources.
Get Notified about Future Security Bulletins
References
Acknowledgement
This issue was reported to HashiCorp by Han Sang-Kyung (HAN-BAMBO) and by additional internal and external parties.
Change History
07 Oct 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:
07 October 2026
Initial Publish date:
07 October 2026
UID
ibm17291625