{"id":"CVE-2026-65593","aliases":["GHSA-9w78-79q7-r4fp"],"title":"n8n: Authenticated SSRF via Dynamic Node Parameters Endpoints Allows Internal Network Access","summary":"n8n: Authenticated SSRF via Dynamic Node Parameters Endpoints Allows Internal Network Access","severity":"medium","cwe":["CWE-918"],"vendor":"n8n","product":"n8n","ecosystem":"npm","affected":["n8n < 1.123.64","n8n >= 2.30.0, < 2.30.1","n8n >= 2.0.0-rc.0, < 2.29.8"],"patched":["n8n 1.123.64","n8n 2.30.1","n8n 2.29.8"],"published":"2026-07-22","updated":"2026-07-22","source":"GHSA","sourceUrl":"https://github.com/advisories/GHSA-9w78-79q7-r4fp","references":[{"url":"https://github.com/n8n-io/n8n/security/advisories/GHSA-9w78-79q7-r4fp"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-65593"},{"url":"https://github.com/n8n-io/n8n/releases/tag/n8n@1.123.64"},{"url":"https://github.com/n8n-io/n8n/releases/tag/n8n@2.29.8"},{"url":"https://github.com/n8n-io/n8n/releases/tag/n8n@2.30.1"},{"url":"https://www.vulncheck.com/advisories/n8n-before-ssrf-via-dynamic-node-parameters"},{"url":"https://github.com/advisories/GHSA-9w78-79q7-r4fp"}],"tags":["ghsa","npm"],"ingestedAt":"2026-07-22T22:06:57.427Z","epss":0.00143,"epssPercentile":0.04006,"slug":"CVE-2026-65593","body":"## Overview\n\n## Impact\n\nEndpoints in `/rest/dynamic-node-parameters/` lacked authorization scopes, making it reachable by any authenticated user with no workflow creation or execution required.\n\nBy 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.\n\n## Patches\nThe 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.\n\n## Workarounds\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Restrict n8n instance access to fully trusted users only.\n- Set `N8N_SSRF_PROTECTION_ENABLED=true` to enable SSRF filtering for private IP ranges and cloud metadata endpoints.\n- Restrict network egress from the n8n host to limit reachable internal services.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.\n\n## Affected packages\n\n- `n8n < 1.123.64`\n- `n8n >= 2.30.0, < 2.30.1`\n- `n8n >= 2.0.0-rc.0, < 2.29.8`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `n8n 1.123.64`\n- `n8n 2.30.1`\n- `n8n 2.29.8`","depth":"sunlit","depthScore":28,"depthScoreParts":{"impact":27.5,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}