{"answers":{"affected":"4 open source packages ship an affected version, including github.com/openbao/openbao and openbao.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46358 exists.","fix":"Upgrade github.com/openbao/openbao to 2.5.4 or later.","what":"CVE-2026-46358 is a medium-severity vulnerability in openbao, published on 7 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-46358 and fix it if it is affected.\n\nWhat it is: CVE-2026-46358 is a medium-severity vulnerability in openbao, published on 7 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46358 exists.\n\nAffected packages and fixed versions:\n- github.com/openbao/openbao (Go): affected all versions; no fix listed\n- github.com/openbao/openbao (Go): affected all versions; fixed in 2.5.4\n- github.com/openbao/openbao (Go): affected all versions; fixed in 2.5.4\n- openbao (Bitnami): affected all versions; fixed in 2.5.4\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-46358/ (Markdown: https://insights.sbomify.com/CVE-2026-46358/index.md)","id":"CVE-2026-46358","markdown":"https://insights.sbomify.com/CVE-2026-46358/index.md","name":"CVE-2026-46358","record":{"aliases":["BIT-openbao-2026-46358","GHSA-q8cj-789h-vg24","GO-2026-5574"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"OpenBao secrets manager","requires_auth":"high_privilege","summary":"OpenBao incorrectly redacts audit logs, exposing authentication headers in cleartext to attackers with audit device access.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"OpenBao is an open source identity-based secrets management system. Prior to version 2.5.4, OpenBao's inline auth functionality incorrectly redacted audit log entries, resulting in non-auth headers being removed and auth-related headers being retained in cleartext. This requires an attacker to compromise access to the audit device. Operators should review leaked source authentication material and rotate it as appropriate. This is fixed in OpenBao v2.5.4.","ecosystems":["Bitnami","Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"OpenBao's Inline Auth Incorrectly Redacted Headers","id":"CVE-2026-46358","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"phpMyFAQ - SQL Injection in CurrentUser::setTokenData via Unescaped OAuth Token Fields","id":"CVE-2026-46359"},"packages":[{"ecosystem":"Bitnami","fixed":["2.5.4"],"introduced":["0"],"last_affected":[],"package":"openbao","purl":"pkg:bitnami/openbao","source":"BIT-openbao-2026-46358"},{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"github.com/openbao/openbao","purl":"pkg:golang/github.com/openbao/openbao","source":"GO-2026-5574"},{"ecosystem":"Go","fixed":["2.5.4"],"introduced":["0"],"last_affected":[],"package":"github.com/openbao/openbao","purl":null,"source":"GHSA-q8cj-789h-vg24"},{"ecosystem":"Go","fixed":["2.5.4"],"introduced":["0"],"last_affected":[],"package":"github.com/openbao/openbao","purl":"pkg:golang/github.com/openbao/openbao","source":"GHSA-q8cj-789h-vg24"}],"prev":{"headline":"HAX CMS NodeJS application Vulnerable to Denial of Service using Malicious Import Request","id":"CVE-2026-46357"},"products":["openbao"],"published":"2026-08-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":"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-11","vendors":["openbao"]},"summary":"OpenBao incorrectly redacts audit logs, exposing authentication headers in cleartext to attackers with audit device access.","url":"https://insights.sbomify.com/CVE-2026-46358/"}