Security Bulletin
Summary
Vault Community Edition and Vault Enterprise did not apply explicit ACL policy deny rules to letter case variants of user and group names in auth methods that treat these names as case-insensitive. This may allow an authenticated user with delegated permissions to modify a protected user or group, potentially leading to privilege escalation. This vulnerability (CVE-2026-128100) 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-128100
DESCRIPTION: Vault matched ACL rules against the request path as supplied, while the LDAP auth method and the RADIUS auth method when configured for case-insensitive names resolved names regardless of letter case. Vault Enterprise SCIM client updates also normalized client names to lowercase. A request that referred to a protected user, group, or SCIM client using different letter case could therefore fail to match an explicit deny rule, be authorized by a broader rule, and still act on the protected entry. This may allow a delegated user to change the policies associated with a protected user or group, which are then granted to anyone who logs in as that user or as a member of that group. This issue requires an authenticated user whose policies grant write access to the broader user, group, or SCIM client path, and a policy that relies on a more specific explicit deny rule to protect an individual entry. Deployments that do not combine these rules are not affected. LDAP user and group management paths are not affected when case_sensitive_names is enabled. RADIUS user management paths are not affected unless case_insensitive_names is enabled, which is disabled by default.
CWE: CWE-178: Improper Handling of Case Sensitivity
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.10.0 up to 2.2.2 |
| Vault Enterprise | affected from 0.10.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, explicit deny rules in ACL policies also match case variants of request paths, subject to the usual rule specificity and the limitations below. This includes secrets engines and other components that treat names as case-sensitive, so operators should review deny rules that are intended to apply to only one letter case form of a path. This update applies to explicit deny rules in ACL policies; to protect individual users, groups, and SCIM clients that treat names as case-insensitive, operators should use explicit deny rules written without a trailing slash rather than narrower capability grants, parameter constraints, or Sentinel policies. Operators should consider tightly scoped policies that grant only the access required, rather than relying on broad allow rules with more specific deny rules to protect sensitive resources. Vault Enterprise delegation tokens are not covered by this fix; operators should avoid combining broad allow rules with more specific deny rules when using delegation tokens.
Get Notified about Future Security Bulletins
References
Acknowledgement
This issue was reported to HashiCorp by Chase Bevan-Thomas.
Change History
13 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:
13 November 2026
Initial Publish date:
13 November 2026
UID
ibm17296772