CVE-2026-45716
Privilege escalation via insecure POST /api/global/users/onboard in Budibase before 3.38.1.
Is CVE-2026-45716 being exploited?
Not confirmed. CVE-2026-45716 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.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-45716?
CVE-2026-45716 is rated High with a CVSS score of 8.8. 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-45716?
Yes. A fix has been recorded for CVE-2026-45716. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-45716 affect?
CVE-2026-45716 affects Budibase (self-hosted). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-45716?
Upgrade to 3.38.1 or newer.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Builder-level users can create a global admin via the vulnerable endpoint, bypassing the admin invite flow when SMTP is unconfigured; full privilege escalation.
Patch when possible
- affected< 3.38.1
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.