Loading vulnerability…
CVE-2026-33757 is a session fixation vulnerability in OpenBao affecting JWT/OIDC authentication flows that use a role configured with callback_mode=direct. In versions prior to 2.5.2, OpenBao does not require explicit user confirmation before completing a direct-mode login. An attacker can initiate an authentication flow, obtain the OpenBao-generated authorization URL, and induce a victim to visit it and authenticate with the identity provider. Because direct callback mode returns to the API and permits polling until token issuance, the victim’s successful authentication can complete the attacker-initiated session rather than a session under the victim’s control. OpenBao 2.5.2 addresses the issue by adding a confirmation screen that requires manual user interaction before completing direct logins.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
callback_mode=direct to eliminate the vulnerable flow. As a compensating control, enforce confirmation for every session at the identity provider or token issuer for the Client ID used by OpenBao so that authentication cannot silently complete an attacker-initiated session. Restrict exposure of the OpenBao API where feasible and monitor audit and identity-provider logs for mismatched source IPs across the same authentication flow, repeated polling behavior, and subsequent token use from unusual origins.Patch, then assume compromise.
callback_mode=direct logins and requires manual user interaction before authentication is finalized. If patching is not immediately possible, reconfigure affected authentication roles to avoid direct callback mode. Review JWT/OIDC role definitions and validate that no production roles continue to use the vulnerable behavior.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Critical session fixation vulnerability in OpenBao OIDC authentication when callback_mode=direct is enabled, allowing an attacker to obtain a victim’s vault token after the victim authenticates via a phishing-delivered auth URL.
An authentication/session confusion vulnerability in OpenBao prior to 2.5.2 involving JWT/OIDC login with `callback_mode=direct`, enabling remote phishing and allowing an attacker to obtain a token issued after a victim visits a crafted URL.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.