{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-128100 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-128100 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-128100 is a medium-severity vulnerability in HashiCorp Vault, published on 13 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-128100 and fix it if it is affected.\n\nWhat it is: CVE-2026-128100 is a medium-severity vulnerability in HashiCorp Vault, published on 13 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-128100 in the wild and no public exploit code.\n\nAffected product: HashiCorp Vault. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-128100/ (Markdown: https://insights.sbomify.com/CVE-2026-128100/index.md)","id":"CVE-2026-128100","markdown":"https://insights.sbomify.com/CVE-2026-128100/index.md","name":"CVE-2026-128100","record":{"aliases":["GHSA-73f8-w3vx-6wjv"],"analysis":null,"analysis_generated_by":null,"assigner":"HashiCorp","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-178","name":"Improper Handling of Case Sensitivity"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Vault vulnerable to ACL deny bypass via case-variant auth method user and group names","id":"CVE-2026-128100","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"n_vendor_status":0,"next":{"headline":"SvelteKit: Protocol-relative module import during server-side route resolution allows cross-origin script execution","id":"CVE-2026-128116"},"nickname":null,"packages":[],"prev":{"headline":"AES key schedule not cleared by the TinyCrypt AES-CTR backend in MCUboot bootutil","id":"CVE-2026-128091"},"products":["Vault","Vault Enterprise"],"published":"2026-11-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-11-13","vendor_status":[],"vendors":["HashiCorp"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-128100/"}