CVE-2026-73303
Authenticated email-change flaw enables account takeover via password reset.
Is CVE-2026-73303 being exploited?
Not confirmed. CVE-2026-73303 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.23% probability of exploitation in the next 30 days.
How severe is CVE-2026-73303?
CVE-2026-73303 is rated High with a CVSS score of 8.2. 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-73303?
Yes. A fix has been recorded for CVE-2026-73303. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73303 affect?
CVE-2026-73303 affects Budibase <3.40.0, account.budibase.app, Self-hosted Budibase instances <3.40.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73303?
Upgrade to Budibase 3.40.0+, revoke sessions and force password resets for affected accounts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker with a victim accountId can change victim email, verify code, reset password, and fully take over the account.
Immediate action required
- affected< 3.40.0
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.