CVE-2026-72849
CSRF lets attackers bind external chat identities to Budibase accounts (pre-3.40.0).
Is CVE-2026-72849 being exploited?
Not confirmed. CVE-2026-72849 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.12% probability of exploitation in the next 30 days.
How severe is CVE-2026-72849?
CVE-2026-72849 is rated High. 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-72849?
Yes. A fix has been recorded for CVE-2026-72849. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72849 affect?
CVE-2026-72849 affects Budibase < 3.40.0, chat-link handoff endpoint. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72849?
Upgrade Budibase to >=3.40.0 and enforce CSRF protections
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
CSRF can bind an attacker-controlled chat identity to a victim account, enabling impersonation, agent actions, and permission inheritance.
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.