CVE-2026-128100 in Vaultinfo

Summary

by MITRE • 11/13/2026

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.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 11/13/2026

The vulnerability identified as CVE-2026-128100 represents a critical access control flaw within HashiCorp Vault’s authentication mechanisms, specifically affecting both the Community Edition and Enterprise versions prior to their respective patched releases. The core issue stems from an inconsistency in how Access Control List policies are enforced against user and group identifiers that differ only by letter case. In many enterprise environments, identity providers such as Active Directory or LDAP treat usernames and group names as case-insensitive entities for authentication purposes. However, Vault’s internal policy engine historically applied explicit deny rules based on exact string matching without normalizing the input to a consistent case format before evaluation. This discrepancy creates a bypass vector where an attacker can exploit the mismatch between the identity provider's normalization logic and Vault's strict literal comparison logic in ACL policies.

From a technical perspective, this flaw allows authenticated users who have been granted delegated permissions for specific resources to circumvent security restrictions by manipulating the casing of their username or group name during API requests. For instance if an administrator has explicitly denied access to modify secrets under a certain path for a user named admin they might assume that variations like Admin ADMIN or AdMiN are also blocked. In reality because Vault did not normalize these identifiers against case-insensitive rules, it treated them as distinct entities and thus failed to apply the deny rule intended for the canonical name. This oversight effectively nullifies the protective intent of explicit ACL policies designed to restrict sensitive operations such as modifying protected users or groups which could lead directly to privilege escalation within the Vault infrastructure.

The operational impact of this vulnerability is severe given that it undermines one of the fundamental principles of least privilege access control in secret management systems. An attacker who successfully exploits this case-sensitivity bypass can modify critical configuration data including policies paths and authentication methods thereby gaining unauthorized administrative capabilities over the entire vault deployment. This could result in the exfiltration of sensitive secrets modification of audit logs to cover tracks or complete takeover of the identity governance framework managed by Vault. Since Vault often serves as the central source of truth for credentials across an organization's infrastructure compromising its integrity poses a significant risk to overall security posture potentially leading to widespread data breaches and system compromise.

This vulnerability aligns with CWE-284 Improper Access Control where insufficient validation or enforcement mechanisms allow unauthorized actions due to logical flaws in access decision processes. Furthermore it maps to MITRE ATT&CK technique T1078 Valid Accounts as the exploitation relies on legitimate but misconfigured credentials being used to escalate privileges through a logic error rather than traditional injection or buffer overflow techniques. The absence of case normalization in policy evaluation represents a common oversight in systems that integrate with external identity providers which often handle casing differently depending on their underlying protocols and configurations such as Kerberos versus LDAP.

To mitigate this risk organizations must immediately upgrade to Vault Community Edition version 2.2.2 or Vault Enterprise versions 1.21.14 and 1.19.25 where the issue has been resolved by implementing robust case-insensitive matching for ACL policy evaluations against user and group names in relevant authentication methods. In addition to upgrading administrators should review existing ACL policies to ensure that explicit deny rules are comprehensive and consider adopting a strategy of normalizing all identity inputs at the application layer or within Vault's configuration where possible before they reach the policy engine. Regular auditing of access logs for unusual casing patterns can also help detect potential exploitation attempts in environments where patching may be delayed due to operational constraints ensuring continuous monitoring remains essential until full remediation is achieved across all deployed instances.

Responsible

HashiCorp

Reservation

11/12/2026

Disclosure

11/13/2026

Moderation

accepted

CPE

ready

EPSS

0.00393

KEV

no

Activities

very low

Sources

Do you know our Splunk app?

Download it now for free!