CVE-2026-35219 Budibase: SSRF in Automation Steps - Webhook, Zapier, N8N, Slack, Discord Bypass IP Blacklist
Authenticated users can bypass IP blacklists in automation steps to perform server-side requests, potentially accessing internal services or cloud metadata.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-35219?
CVE-2026-35219 is a high-severity server-side request forgery vulnerability in budibase, published on 17 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Budibase is an open-source low-code platform. Prior to 3.41.3, automation steps in packages/server/src/automations/steps/outgoingWebhook.ts, packages/server/src/automations/steps/zapier.ts, packages/server/src/automations/steps/n8n.ts, packages/server/src/automations/steps/slack.ts, and packages/server/src/automations/steps/discord.ts use node-fetch on user-provided URLs without the BLACKLIST_IPS enforcement used by the REST integration, allowing an authenticated user to make server-side requests to cloud metadata and internal services. This issue is fixed in version 3.41.3.
Weakness: CWE-918
Which versions are affected by CVE-2026-35219?
2 open source packages ship an affected version, including @budibase/server.
| Package | Affected | Fixed in |
|---|---|---|
@budibase/server npm | All versions | 3.41.3 |
@budibase/server npm | All versions | 3.41.3 |
How do I fix CVE-2026-35219?
Upgrade @budibase/server to 3.41.3 or later.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-35219 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35219 exists.
Sources
Also known as GHSA-5fpj-28rv-84r7.