{"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-33757 in the wild and no public exploit code.","fix":"Upgrade github.com/openbao/openbao to 0.0.0-20260325142553-e32103951925 or later.","what":"CVE-2026-33757 is a critical vulnerability in openbao, published on 27 Mar 2026."},"fix_prompt":"Check this codebase for CVE-2026-33757 and fix it if it is affected.\n\nWhat it is: CVE-2026-33757 is a critical vulnerability in openbao, published on 27 Mar 2026. \nExploitation: There is no known exploitation of CVE-2026-33757 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-20260325142553-e32103951925\n- github.com/openbao/openbao (Go): affected all versions; fixed in 0.0.0-20260325142553-e32103951925\n- github.com/openbao/openbao (Go): affected all versions; fixed in 0.0.0-20260325142553-e32103951925\n- openbao (Bitnami): affected all versions; fixed in 2.5.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-33757/ (Markdown: https://insights.sbomify.com/CVE-2026-33757/index.md)","id":"CVE-2026-33757","markdown":"https://insights.sbomify.com/CVE-2026-33757/index.md","name":"CVE-2026-33757","record":{"aliases":["BIT-openbao-2026-33757","GHSA-7q7g-x6vg-xpc3","GO-2026-4860"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[{"product":"openbao","vendor":"openbao"}],"cvss":{"score":9.6,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-384","name":"Session Fixation"}],"description":"OpenBao is an open source identity-based secrets management system. Prior to version 2.5.2, OpenBao does not prompt for user confirmation when logging in via JWT/OIDC and a role with `callback_mode` set to `direct`. This allows an attacker to start an authentication request and perform \"remote phishing\" by having the victim visit the URL and automatically log-in to the session of the attacker. Despite being based on the authorization code flow, the  `direct` mode calls back directly to the API and allows an attacker to poll for an OpenBao token until it is issued. Version 2.5.2 includes an additional confirmation screen for `direct` type logins that requires manual user interaction in order to finish the authentication. This issue can be worked around either by removing any roles with `callback_mode=direct` or enforcing confirmation for every session on the token issuer side for the Client ID used by OpenBao.","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 lacks user confirmation for OIDC direct callback mode","id":"CVE-2026-33757","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":null,"year":"2026"},"n_packages":4,"n_references":3,"next":{"headline":"OpenBao has Reflected XSS in its OIDC authentication error message","id":"CVE-2026-33758"},"packages":[{"ecosystem":"Bitnami","fixed":["2.5.2"],"introduced":["0"],"last_affected":[],"package":"openbao","purl":"pkg:bitnami/openbao","source":"BIT-openbao-2026-33757"},{"ecosystem":"Go","fixed":["0.0.0-20260325142553-e32103951925"],"introduced":["0"],"last_affected":[],"package":"github.com/openbao/openbao","purl":null,"source":"GHSA-7q7g-x6vg-xpc3"},{"ecosystem":"Go","fixed":["0.0.0-20260325142553-e32103951925"],"introduced":["0"],"last_affected":[],"package":"github.com/openbao/openbao","purl":"pkg:golang/github.com/openbao/openbao","source":"GHSA-7q7g-x6vg-xpc3"},{"ecosystem":"Go","fixed":["0.0.0-20260325142553-e32103951925"],"introduced":["0"],"last_affected":[],"package":"github.com/openbao/openbao","purl":"pkg:golang/github.com/openbao/openbao","source":"GO-2026-4860"}],"prev":{"headline":"Saleor Affected by Denial of Service via Unbounded GraphQL Query Batching","id":"CVE-2026-33756"},"products":["openbao"],"published":"2026-03-27","related":[{"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":"total"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["openbao"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-33757/"}