cve.bz

CVE-2026-128100 Vault vulnerable to ACL deny bypass via case-variant auth method user and group names

6.5 mediumFix available

Medium (6.5) in hashicorp.

On this page
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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-178 Improper Handling of Case Sensitivity
Published
Modified
Assigned by
HashiCorp (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-128100 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-128100?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-128100?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-128100 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-128100

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-128100](https://cve.bz/cve/badge/CVE-2026-128100.svg)](https://cve.bz/cve/CVE-2026-128100)

HTML:

<a href="https://cve.bz/cve/CVE-2026-128100"><img src="https://cve.bz/cve/badge/CVE-2026-128100.svg" alt="CVE-2026-128100"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
HashiCorp Vaultfrom 0.10.0 before 2.2.2
HashiCorp Vault Enterprisefrom 0.10.0 before 2.2.2

Fixed in

ProductFixed in
HashiCorp Vault Enterprise1.19.25
HashiCorp Vault Enterprise1.21.14

Fix and patched versions

  • HashiCorp Vault Enterprise: fixed in 1.19.25
  • HashiCorp Vault Enterprise: fixed in 1.21.14

References

Check your stackJSON