CVE-2026-73302
OIDC email verification bypass enables SSO account takeover.
Is CVE-2026-73302 being exploited?
Not confirmed. CVE-2026-73302 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.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-73302?
CVE-2026-73302 is rated Critical with a CVSS score of 9.0. 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-73302?
Yes. A fix has been recorded for CVE-2026-73302. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73302 affect?
CVE-2026-73302 affects Budibase < 3.39.30, backend-core OIDC middleware (packages/backend-core). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73302?
Upgrade to Budibase 3.39.30 and enforce email_verified in IdP configurations.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
SSO account takeover: attacker can link a new IdP identity to a victim Budibase account and inherit the victim's roles (privilege escalation).
Immediate action required
- affected< 3.39.30
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.