{"answers":{"affected":"1 open source package ship an affected version, including vault.","exploited":"There is no known exploitation of CVE-2026-105820 in the wild and no public exploit code.","fix":"Upgrade vault to a fixed version for your release line: 1.19.23, 1.20.17, 1.21.12 or 2.1.2.","what":"CVE-2026-105820 is a medium-severity path traversal vulnerability in HashiCorp Vault Enterprise, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-105820 and fix it if it is affected.\n\nWhat it is: CVE-2026-105820 is a medium-severity path traversal vulnerability in HashiCorp Vault Enterprise, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-105820 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- vault (Bitnami): affected from 0.0.1; fixed in 1.19.23, 1.20.17, 1.21.12, 2.1.2\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-105820/ (Markdown: https://insights.sbomify.com/CVE-2026-105820/index.md)","id":"CVE-2026-105820","markdown":"https://insights.sbomify.com/CVE-2026-105820/index.md","name":"CVE-2026-105820","record":{"aliases":["BIT-vault-2026-105820","GHSA-4rj6-p7m7-65jf","MINI-ffm2-qcfx-3vqc"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Vault Enterprise","requires_auth":"low_privilege","summary":"Attackers can use path traversal in policy names to access capabilities from other namespaces, including root, in Vault Enterprise.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"HashiCorp","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Vault's ACL policy cache allowed namespace traversal when policy names contained path traversal constructs. This may allow a token assigned specially crafted policy names to use the capabilities of policies defined in other namespaces, including the root namespace. This vulnerability (CVE-2026-105820) is fixed in Vault Enterprise 2.1.2, 1.21.12, 1.20.17, and 1.19.23. Vault Community Edition does not support namespaces, and is not affected.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Vault ACL Policy Cache Vulnerable to Cross-Namespace Policy Resolution","id":"CVE-2026-105820","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":1,"n_references":1,"next":{"headline":"This CVE ID has been rejected as a duplicate.","id":"CVE-2026-105823"},"packages":[{"ecosystem":"Bitnami","fixed":["1.19.23","1.20.17","1.21.12","2.1.2"],"introduced":["0.0.1","1.20.0","1.21.0","2.0.0"],"last_affected":[],"package":"vault","purl":"pkg:bitnami/vault","source":"BIT-vault-2026-105820"}],"prev":{"headline":"Vault PKI ACME Issues Certificate With Unvalidated SANs","id":"CVE-2026-105818"},"products":["Vault Enterprise"],"published":"2026-10-07","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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-10-08","vendors":["HashiCorp"]},"summary":"Attackers can use path traversal in policy names to access capabilities from other namespaces, including root, in Vault Enterprise.","url":"https://insights.sbomify.com/CVE-2026-105820/"}