Vulnerability 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.
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Openbao | Openbao | < 2.5.2 |
Related Weaknesses (CWE)
References
- https://datatracker.ietf.org/doc/html/rfc8628#section-5.4Technical Description
- https://github.com/openbao/openbao/commit/e32103951925723e9787e33886ab6b6ec20f49Patch
- https://github.com/openbao/openbao/security/advisories/GHSA-7q7g-x6vg-xpc3Vendor Advisory
FAQ
What is CVE-2026-33757?
CVE-2026-33757 is a vulnerability with a CVSS score of 9.6 (CRITICAL). 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` s...
How severe is CVE-2026-33757?
CVE-2026-33757 has been rated CRITICAL with a CVSS base score of 9.6/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2026-33757?
Check the references section above for vendor advisories and patch information. Affected products include: Openbao Openbao.