What is CVE-2026-35219?

CVE-2026-35219 is Budibase: SSRF in Automation Steps - Webhook, Zapier, N8N, Slack, Discord Bypass IP Blacklist. The supplied enrichment data classifies it as SSRF mapped to CWE-918 Server-Side Request Forgery (SSRF).

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-35219. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-35219 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

A public PoC is not confirmed from current sources for CVE-2026-35219. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with cloud metadata access logs, egress proxy logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-35219 using CVSS 7.1, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

highSSRF

CVE-2026-35219

CVE-2026-35219 — Budibase: SSRF in Automation Steps - Webhook, Zapier, N8N, Slack, Discord Bypass IP Blacklist

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.

Published Aug 17, 2026Updated Aug 17, 2026Sources: NVD, Budibase (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

ahead of 0% of scored CVEs

Affects

Budibase

2 products listed

CVSS base

7.1

high

Remediation

The vendor's own words where we have them.

Upgrade @budibase/server to 3.41.3 or later (npm advisory GHSA-5fpj-28rv-84r7).

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Budibase	budibase	< 3.41.3	Vulnerable
npm	@budibase/server	< 3.41.3	Vulnerable

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.1	CVSS 4.0	high	—	—	Budibase (CNA)

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-918 · Server-Side Request Forgery (SSRF)

Read Application Data
Execute Unauthorized Code or Commands::

Weakness & attack patterns

CWE-918Server-Side Request Forgery (SSRF)

Inferred from the weakness class — not observed against this CVE.

CAPEC-664 · Server Side Request Forgery

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Search application, proxy, and WAF logs for requests touching /server/src/automations/steps/outgoingWebhook.ts, /server/src/automations/steps/zapier.ts, /server/src/automations/steps/n8n.ts, /server/src/automations/steps/slack.ts, /server/src/automations/steps/discord.ts.

cloud metadata access logsegress proxy logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 7.1
Aug 17, 2026 · NVD
Initial · CVE published
Aug 17, 2026 · NVD
Added · GHSA-5fpj-28rv-84r7 published (high)
Aug 14, 2026 · GitHub Security Advisory

References

5 on the record

github.com/Budibase/budibase/commit/cc07563a6b0fc0f91c51aae295952b1295546a90
Exploit, Third Party Advisory, Mitre
github.com/Budibase/budibase/pull/19328
Exploit, Third Party Advisory, Mitre
github.com/Budibase/budibase/releases/tag/3.41.3
Exploit, Third Party Advisory, Mitre
github.com/Budibase/budibase/security/advisories/GHSA-5fpj-28rv-84r7
Exploit, Third Party Advisory, Mitre
github.com/advisories/GHSA-5fpj-28rv-84r7
Exploit, Third Party Advisory

Elsewhere on this site

Budibaseevery CVE for this vendor
npmevery CVE for this vendor
SSRFsame class
CWE-918other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-35219 is Budibase: SSRF in Automation Steps - Webhook, Zapier, N8N, Slack, Discord Bypass IP Blacklist, a high vulnerability affecting budibase, @budibase/server from Budibase, npm. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-35219. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-35219. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.1 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.