Is CVE-2026-35219 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-35219 being exploited in the wild.

How severe is CVE-2026-35219?

High severity, with a CVSS score of 4, published 14 August 2026.

Which products and versions are affected?

@budibase/server (npm) < 3.41.3, SEMVER:introduced=0,fixed=3.41.3.

Is there a fix for CVE-2026-35219?

Yes. @budibase/server (npm): upgrade to 3.41.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-35219 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-35219?

Check whether you run @budibase/server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-35219: Budibase automation SSRF in webhook and integration steps

Q: Is there a fix for CVE-2026-35219?

Yes. @budibase/server (npm): upgrade to 3.41.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-35219 attacked?

It is attacked over the network, in a web application.

Q: Am I affected by CVE-2026-35219?

Check whether you run @budibase/server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-35219 · Severity: high · CVSS 4 · Published 2026-08-14

Budibase is an open-source low-code platform that allows users to build applications and automations. The automation features (webhooks, Zapier, n8n, Slack, Discord integrations) make server-side HTTP requests to user-specified URLs, but completely bypass the IP blacklist protection that exists elsewhere in the system. An authenticated attacker can exploit this to access internal services, cloud metadata endpoints, databases, and admin panels on private networks that should be protected.

Technologies: @budibase/server (npm). Vendors: npm.

Quick answers

Is CVE-2026-35219 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-35219 being exploited in the wild.
How severe is CVE-2026-35219?: High severity, with a CVSS score of 4, published 14 August 2026.
Which products and versions are affected?: @budibase/server (npm) < 3.41.3, SEMVER:introduced=0,fixed=3.41.3.
Is there a fix for CVE-2026-35219?: Yes. @budibase/server (npm): upgrade to 3.41.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-35219 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-35219?: Check whether you run @budibase/server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@budibase/server (npm): upgrade to 3.41.3 or later
```
npm install @budibase/server@3.41.3
```

Technical details

This is a Server-Side Request Forgery (SSRF) vulnerability in Budibase's automation step handlers (CWE-918). Multiple automation step types—outgoing webhook, Zapier, n8n, Slack, Discord—use fetch() directly without any IP validation checks in their respective files (outgoingWebhook.ts line 69, zapier.ts line 34, n8n.ts line 53, slack.ts line 20, discord.ts line 29). Additionally, the REST API integration's IP blacklist defaults to an empty state when the BLACKLIST_IPS environment variable is not configured, rendering it ineffective by default. The attack vector requires authentication (user must be able to create automations), but no user interaction beyond that is necessary. An attacker can specify arbitrary URLs pointing to private IP ranges (127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 169.254.0.0/16) or cloud metadata endpoints (http://169.254.169.254/) to retrieve sensitive information. The vulnerability is fixed in version 3.41.3, where blacklist checks have been applied to all outbound HTTP requests.

Affected products

Budibase @budibase/server <3.41.3

Identifiers

CVE-2026-35219
GHSA-5fpj-28rv-84r7

Timeline

2026-08-14: disclosed
2026-08-14: patched: Version 3.41.3 released on 2026-08-04

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.