Skip to content
n8nGHSA-9w78-79q7-r4fp

n8n: Authenticated SSRF via Dynamic Node Parameters Endpoints Allows Internal Network Access

MediumCVE-2026-65593 · Published Jul 22, 2026

## Impact Endpoints in `/rest/dynamic-node-parameters/` lacked authorization scopes, making it reachable by any authenticated user with no workflow creation or execution required. By supplying an absolute URL in the routing configuration, a caller could override the node type's declared baseURL, defeating the restriction meant to confine requests to the node's own upstream service. With SSRF protection disabled by default (`N8N_SSRF_PROTECTION_ENABLED=false`), this let an authenticated user make the n8n server issue HTTP requests to arbitrary internal targets. ## Patches The issue has been fixed in n8n versions 1.123.64, 2.29.8, and 2.30.1. Users should upgrade to this version or later to remediate the vulnerability. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict n8n instance access to fully trusted users only. - Set `N8N_SSRF_PROTECTION_ENABLED=true` to enable SSRF filtering for private IP ranges and cloud metadata endpoints. - Restrict network egress from the n8n host to limit reachable internal services. These workarounds do not fully remediate the risk and should only be used as short-...

GitHub advisory

Affected versions

PackageAffectedFixed in
n8n
npm
< 1.123.641.123.64
>= 2.30.0, < 2.30.12.30.1
>= 2.0.0-rc.0, < 2.29.82.29.8
Details and references

## Impact Endpoints in `/rest/dynamic-node-parameters/` lacked authorization scopes, making it reachable by any authenticated user with no workflow creation or execution required. By supplying an absolute URL in the routing configuration, a caller could override the node type's declared baseURL, defeating the restriction meant to confine requests to the node's own upstream service. With SSRF protection disabled by default (`N8N_SSRF_PROTECTION_ENABLED=false`), this let an authenticated user make the n8n server issue HTTP requests to arbitrary internal targets. ## Patches The issue has been fixed in n8n versions 1.123.64, 2.29.8, and 2.30.1. Users should upgrade to this version or later to remediate the vulnerability. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict n8n instance access to fully trusted users only. - Set `N8N_SSRF_PROTECTION_ENABLED=true` to enable SSRF filtering for private IP ranges and cloud metadata endpoints. - Restrict network egress from the n8n host to limit reachable internal services. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

CVSS 4.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:H/SI:L/SA:N
Severity from
GitHub (reviewed advisory)
Weakness
CWE-918
Also known as
CVE-2026-65593

More n8n advisories

All n8n
Advisory
n8n: Snowflake Node executeQuery Operation Allows SQL Injection via Unparameterized Expression Interpolation
MediumJul 22
n8n: SQL injection
MediumJul 22
n8n: Cross-Tenant Module-Cache Poisoning in the JS Task Runner
MediumJul 22
n8n: Custom Header Credential Values Leaked in Plaintext into LLM Node Execution Data
MediumJul 22
n8n: Unauthenticated Endpoint Allows Cancellation of Any User's Active Test Webhook
MediumJul 22
n8n: GraphQL Node Bypasses "Allowed HTTP Request Domains" Restriction
MediumJul 22

Critical advisories by email

Wednesdays: the week’s critical and high advisories in the AI and data stack, with the fixed versions. Only in weeks that have some.

Double opt-in. Unsubscribe any time.