Vulnerability DatabaseCVE-2026-128100

CVE-2026-128100: 
HashiCorp Vault vulnerability analysis and mitigation

Overview

CVE-2026-128100 is an authorization bypass vulnerability in HashiCorp Vault Community Edition and Vault Enterprise caused by improper handling of case sensitivity in ACL policy enforcement. Vault 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, potentially allowing privilege escalation. Affected versions span from 0.10.0 up to (but not including) 2.2.2 for both Community and Enterprise editions. The vulnerability was published on November 13, 2026, and carries a CVSS v3.1 base score of 6.5 (Medium) (GitHub Advisory, HashiCorp Advisory).

Technical details

The root cause is classified as CWE-178 (Improper Handling of Case Sensitivity): Vault's ACL engine failed to normalize the case of user and group names before evaluating explicit deny rules, while certain auth methods treated those names as case-insensitive. An authenticated attacker with delegated administrative permissions could reference a protected user or group using a case variant (e.g., Admin instead of admin) to bypass the deny rule and perform modifications that should be blocked. Exploitation requires network access and high privileges (delegated permissions), but no user interaction or special attack complexity beyond crafting the case-variant name (GitHub Advisory, HashiCorp Advisory).

Impact

Successful exploitation allows an authenticated user with delegated permissions to modify protected users or groups within Vault, bypassing intended ACL deny policies. This can lead to privilege escalation within the Vault environment, enabling an attacker to grant themselves or others elevated access to secrets, policies, or auth method configurations. While confidentiality impact is rated None (no direct data exfiltration via this flaw), integrity and availability are both rated High, as unauthorized modifications to users or groups could disrupt access controls or cause denial of service to legitimate users (GitHub Advisory).

Exploitability

There is no public proof-of-concept exploit code and no evidence of in-the-wild exploitation at the time of disclosure (HashiCorp Advisory). The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The EPSS score is 0.0, reflecting a very low probability of exploitation in the near term. Exploitation is not automatable and requires an authenticated attacker with delegated permissions, limiting the attack surface significantly (GitHub Advisory).

Exploitation steps

  1. Reconnaissance: Identify a target Vault instance running a vulnerable version (0.10.0 through 2.2.2) with an auth method that treats user or group names as case-insensitive (e.g., LDAP, GitHub, or similar).
  2. Obtain delegated permissions: Authenticate to Vault using an account that has been granted delegated administrative permissions over users or groups, but is explicitly denied access to specific protected users or groups via ACL policy.
  3. Identify protected target: Enumerate users or groups in the auth method to identify a protected user or group (e.g., admin) that is subject to an explicit ACL deny rule.
  4. Craft case-variant request: Submit a Vault API request targeting the protected user or group using a letter case variant of the name (e.g., Admin, ADMIN, or aDmIn) that bypasses the deny rule evaluation.
  5. Modify protected entity: Successfully modify the protected user or group (e.g., alter group membership, policies, or metadata), achieving privilege escalation within the Vault environment (HashiCorp Advisory, GitHub Advisory).

Indicators of compromise

  • Logs: Vault audit logs showing API requests to user or group management endpoints (e.g., /v1/auth/<method>/groups/<name> or /v1/auth/<method>/users/<name>) where the name uses unexpected letter casing (mixed case, all caps, etc.) for known protected entities.
  • Logs: Vault audit log entries reflecting successful write or update operations on users or groups that should have been denied by ACL policy, particularly from accounts with delegated but restricted permissions.
  • Network: Repeated API calls to Vault auth method user/group management endpoints from a single authenticated identity, especially with variations in the casing of entity names.
  • Vault Audit: Changes to group membership or policy assignments for privileged groups (e.g., admin, superuser) performed by accounts not expected to have that access, visible in Vault's audit log.

Mitigation and workarounds

HashiCorp has released patches addressing this vulnerability: upgrade to Vault Community Edition 2.2.2 or Vault Enterprise 2.2.2, 1.21.14, or 1.19.25. As interim mitigations, administrators should audit and restrict delegated permissions to only those users who strictly require them, and review ACL policies to ensure deny rules are applied as intended. There are no documented configuration-only workarounds that fully remediate the issue without patching (HashiCorp Advisory, GitHub Advisory).

Community reactions

The vulnerability was disclosed by HashiCorp via their security advisory forum (HCSEC-2026-58) on November 13, 2026, with patches released simultaneously. Community discussion on Mastodon/infosec.exchange noted the disclosure, and the issue was indexed by standard vulnerability tracking platforms shortly after publication. No significant independent researcher commentary or media coverage beyond routine vulnerability tracking has been observed at this time (HashiCorp Advisory).

Additional resources


Source: This report was generated using AI

Related HashiCorp Vault vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-92738MEDIUM6.8
  • HashiCorp Vault logoHashiCorp Vault
  • cpe:2.3:a:hashicorp:vault
NoYesNov 13, 2026
CVE-2026-128100MEDIUM6.5
  • HashiCorp Vault logoHashiCorp Vault
  • cpe:2.3:a:hashicorp:vault
NoYesNov 13, 2026
CVE-2026-93335MEDIUM6.5
  • HashiCorp Vault logoHashiCorp Vault
  • cpe:2.3:a:hashicorp:vault
NoYesNov 13, 2026
CVE-2026-92735MEDIUM5.9
  • HashiCorp Vault logoHashiCorp Vault
  • cpe:2.3:a:hashicorp:vault
NoYesNov 13, 2026
CVE-2026-93333LOW2.7
  • HashiCorp Vault logoHashiCorp Vault
  • cpe:2.3:a:hashicorp:vault
NoYesNov 13, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management