CVE-2026-54350
Unauthenticated user can read/modify all documents via crafted queries in Budibase (pre-3.39.12).
Is CVE-2026-54350 being exploited?
Not confirmed. CVE-2026-54350 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.54% probability of exploitation in the next 30 days.
How severe is CVE-2026-54350?
CVE-2026-54350 is rated Critical with a CVSS score of 10.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-54350?
Yes. A fix has been recorded for CVE-2026-54350. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-54350 affect?
CVE-2026-54350 affects Budibase (server) pre-3.39.12. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-54350?
Upgrade to 3.39.12+; audit apps; enforce CSRF where applicable.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated access can read/modify backend docs; lacks CSRF enforcement; potential data exposure and tampering in published apps.
Immediate action required
- affected< 3.39.12
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.