CVE-2026-33757
OpenBao auth bypass via direct OIDC callback enables remote phishing
Is CVE-2026-33757 being exploited?
Not confirmed. CVE-2026-33757 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.
How severe is CVE-2026-33757?
CVE-2026-33757 is rated Critical with a CVSS score of 9.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-33757?
Yes. A fix has been recorded for CVE-2026-33757. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-33757 affect?
CVE-2026-33757 affects OpenBao <= 2.5.1, OpenBao 2.x (auth flow with direct callback). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-33757?
Upgrade to 2.5.2; remove direct callback roles; require per-session confirmation
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote phishing lets attacker obtain victim OpenBao token without consent, enabling session hijack and secret access.
Patch when possible
- affected< 2.5.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.