Executive brief
OpenBao is an open-source tool used by organizations to manage and protect sensitive information like passwords and encryption keys. A security flaw in its login process allows an attacker to trick a user into unintentionally authorizing a login session for the attacker. If successful, the attacker could gain full access to the victim's secrets and credentials, potentially leading to a total compromise of sensitive corporate data.
Technical details
A session fixation vulnerability exists in OpenBao's JWT/OIDC authentication backend when a role is configured with `callback_mode` set to `direct`. The implementation lacks a manual confirmation step, allowing an attacker to initiate an authentication request and lure a victim to the verification URL. Because the `direct` mode communicates back to the API without user intervention, the attacker can poll the API until a token is issued to their own session upon the victim's successful authentication. This is a violation of the security considerations in RFC 8628 (OAuth 2.0 Device Authorization Grant). The vulnerability is resolved in version 2.5.2 by introducing a mandatory confirmation screen.
Affected products
- OpenBao OpenBao < 2.5.2
Timeline
- 2026-03-25: patched: Fix committed to repository
- 2026-03-27: disclosed: Initial advisory published
References
- https://datatracker.ietf.org/doc/html/rfc8628
- https://github.com/openbao/openbao/commit/e32103951925723e9787e33886ab6b6ec20f4964
- https://github.com/openbao/openbao/security/advisories/GHSA-7q7g-x6vg-xpc3
- https://access.redhat.com/security/cve/CVE-2026-33757
- https://bugzilla.redhat.com/show_bug.cgi?id=2452269
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33757.json