Skip to content
Applications

CVE-2026-72851

9.0
Critical
EPSS 0.29%Patch availableAug 14, 2026

Unauthenticated SQL injection in Budibase webhook EXECUTE_QUERY

common questions

Is CVE-2026-72851 being exploited?

Not confirmed. CVE-2026-72851 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.29% probability of exploitation in the next 30 days.

How severe is CVE-2026-72851?

CVE-2026-72851 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-72851?

Yes. A fix has been recorded for CVE-2026-72851. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-72851 affect?

CVE-2026-72851 affects Budibase < 3.40.0, Budibase webhook-triggered automations (EXECUTE_QUERY), Connected datasources (e.g., Snowflake). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72851?

Upgrade Budibase to >=3.40.0, restrict/validate webhooks, and block public webhook endpoints.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Budibase < 3.40.0Budibase webhook-triggered automations (EXECUTE_QUERY)Connected datasources (e.g., Snowflake)
impact

Unauthenticated SQLi via webhook lets attackers run queries with builder DB creds, enabling data exfiltration, modification, and persistence in connected DBs (e.g., Snowflake).

action required

Immediate action required

affected versions
budibase server
  • affected< 3.40.0
vendor says fixed in3.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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free