Server-side Request Forgery (SSRF) Affecting n8n package, versions <1.123.64>=2.0.0-rc.0 <2.29.8>=2.30.0 <2.30.1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-N8N-18322064
- published27 Jul 2026
- disclosed22 Jul 2026
- credital1z4deh
Introduced: 22 Jul 2026
NewCVE-2026-65593 (opens in a new tab)How to fix?
Upgrade n8n to version 1.123.64, 2.29.8, 2.30.1 or higher.
Overview
n8n is a n8n Workflow Automation Tool
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in the /rest/dynamic-node-parameters/ endpoint due to insufficient authorization checks and the ability to supply an absolute URL in the routing configuration. An attacker can access internal network resources by making the server issue HTTP requests to arbitrary internal targets.
Note: This is only exploitable if SSRF protection is disabled (N8N_SSRF_PROTECTION_ENABLED=false). This is the default setting.
Workaround
This vulnerability can be mitigated by restricting instance access to trusted users, enabling SSRF filtering by setting N8N_SSRF_PROTECTION_ENABLED=true, and limiting network egress from the host.