{"answers":{"affected":"4 open source packages ship an affected version, including github.com/openbao/openbao and openbao. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-42186 in the wild and no public exploit code.","fix":"Upgrade github.com/openbao/openbao to 0.0.0-20260420173541-6d2e0506e2b4 or later.","what":"CVE-2026-42186 is a low-severity vulnerability in openbao, published on 14 May 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-42186 and fix it if it is affected.\n\nWhat it is: CVE-2026-42186 is a low-severity vulnerability in openbao, published on 14 May 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-42186 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/openbao/openbao (Go): affected all versions; fixed in 0.0.0-20260420173541-6d2e0506e2b4\n- github.com/openbao/openbao (Go): affected all versions; fixed in 0.0.0-20260420173541-6d2e0506e2b4\n- github.com/openbao/openbao (Go): affected all versions; fixed in 0.0.0-20260420173541-6d2e0506e2b4\n- openbao (Bitnami): affected all versions; fixed in 2.5.3\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-42186/ (Markdown: https://insights.sbomify.com/CVE-2026-42186/index.md)","id":"CVE-2026-42186","markdown":"https://insights.sbomify.com/CVE-2026-42186/index.md","name":"CVE-2026-42186","record":{"aliases":["BIT-openbao-2026-42186","GHSA-vv66-6rp4-wr4f","GO-2026-5674"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","other"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenBao secrets manager","requires_auth":"low_privilege","summary":"Incomplete namespace deletion in OpenBao may leave residual data and active leases, potentially exposing sensitive information or causing state inconsistencies.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"openbao","vendor":"openbao"}],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-212","name":"Improper Removal of Sensitive Information Before Storage or Transfer"}],"description":"OpenBao is an open source identity-based secrets management system. Prior to 2.5.3, when OpenBao's initial namespace deletion fails, subsequent retries fail to properly remove all data before marking the namespace as deleted. This can affect any outstanding leases as well as potentially leaving unrelated storage entries around. This vulnerability is fixed in 2.5.3.","ecosystems":["Bitnami","Go"],"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":"OpenBao's Namespace Deletion May Not Delete Data Properly","id":"CVE-2026-42186","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":4,"n_references":3,"next":{"headline":"Geyser: Server-Side Request Forgery (SSRF) via Player Head Texture URL","id":"CVE-2026-42188"},"packages":[{"ecosystem":"Bitnami","fixed":["2.5.3"],"introduced":["0"],"last_affected":[],"package":"openbao","purl":"pkg:bitnami/openbao","source":"BIT-openbao-2026-42186"},{"ecosystem":"Go","fixed":["0.0.0-20260420173541-6d2e0506e2b4"],"introduced":["0"],"last_affected":[],"package":"github.com/openbao/openbao","purl":null,"source":"GHSA-vv66-6rp4-wr4f"},{"ecosystem":"Go","fixed":["0.0.0-20260420173541-6d2e0506e2b4"],"introduced":["0"],"last_affected":[],"package":"github.com/openbao/openbao","purl":"pkg:golang/github.com/openbao/openbao","source":"GHSA-vv66-6rp4-wr4f"},{"ecosystem":"Go","fixed":["0.0.0-20260420173541-6d2e0506e2b4"],"introduced":["0"],"last_affected":[],"package":"github.com/openbao/openbao","purl":"pkg:golang/github.com/openbao/openbao","source":"GO-2026-5674"}],"prev":{"headline":"People: Privilege Escalation via Missing Role Ceiling in Mail Domain Invitation","id":"CVE-2026-42185"},"products":["openbao"],"published":"2026-05-14","related":[{"cvss_score":9.6,"headline":"OpenBao lacks user confirmation for OIDC direct callback mode","id":"CVE-2026-33757","kev_date_added":null,"published":"2026-03-27"},{"cvss_score":9.4,"headline":"OpenBao has Reflected XSS in its OIDC authentication error message","id":"CVE-2026-33758","kev_date_added":null,"published":"2026-03-27"},{"cvss_score":9.1,"headline":"OpenBao: Privileged Operator May Execute Code on the Underlying Host","id":"CVE-2025-54997","kev_date_added":null,"published":"2025-08-09"},{"cvss_score":7.5,"headline":"OpenBao Privileged Operator Identity Group Root Escalation","id":"CVE-2025-64761","kev_date_added":null,"published":"2025-11-25"},{"cvss_score":7.5,"headline":"OpenBao vulnerable to denial of service via malicious JSON request processing","id":"CVE-2025-59043","kev_date_added":null,"published":"2025-10-17"},{"cvss_score":7.2,"headline":"OpenBao Root Namespace Operator May Elevate Token Privileges","id":"CVE-2025-54996","kev_date_added":null,"published":"2025-08-09"},{"cvss_score":6.9,"headline":"OpenBao Vulnerable to Unauthenticated Rekey Operation Cancellation","id":"CVE-2025-52894","kev_date_added":null,"published":"2025-06-25"}],"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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-05-14","vendors":["openbao"]},"summary":"Incomplete namespace deletion in OpenBao may leave residual data and active leases, potentially exposing sensitive information or causing state inconsistencies.","url":"https://insights.sbomify.com/CVE-2026-42186/"}