CVE-2026-65593 Overview
CVE-2026-65593 is a Server-Side Request Forgery (SSRF) vulnerability affecting n8n workflow automation platform versions prior to 1.123.64. The flaw resides in the dynamic-node-parameters endpoints, which lack proper authorization scopes. Authenticated attackers can supply absolute URLs within routing configuration to override the intended baseURL restrictions. When SSRF protection is disabled, the n8n server issues HTTP requests to arbitrary internal targets chosen by the attacker. This exposes internal services, cloud metadata endpoints, and other network resources normally unreachable from the internet.
Critical Impact
Authenticated attackers can pivot from n8n instances into internal network services, potentially reaching cloud metadata endpoints, internal APIs, and other non-public infrastructure via [CWE-918] SSRF.
Affected Products
- n8n versions prior to 1.123.64
- n8n self-hosted deployments with SSRF protection disabled
- n8n instances exposing dynamic-node-parameters endpoints to authenticated users
Discovery Timeline
- 2026-07-22 - CVE-2026-65593 published to NVD
- 2026-07-22 - Last updated in NVD database
Technical Details for CVE-2026-65593
Vulnerability Analysis
The vulnerability exists in n8n's dynamic-node-parameters endpoints. These endpoints resolve runtime parameters for nodes and issue HTTP requests based on routing configuration supplied by the client. The endpoints do not enforce authorization scopes, allowing any authenticated user to invoke them regardless of privilege level.
n8n normally restricts outbound requests through a configured baseURL. However, the routing configuration accepts absolute URLs that override this restriction. When SSRF protection is disabled in the deployment, the server follows attacker-supplied URLs without validating the destination. This gives authenticated attackers a request-forwarding primitive from the n8n host into internal networks.
Root Cause
Two defects combine to produce the vulnerability. First, the dynamic-node-parameters endpoints lack authorization scope checks, exposing routing functionality to low-privilege authenticated users. Second, the routing logic honors absolute URLs supplied by callers and does not enforce the configured baseURL boundary. Categorized as [CWE-918] Server-Side Request Forgery, the flaw allows the server's network position to be abused for reconnaissance and interaction with internal resources.
Attack Vector
An authenticated attacker crafts a request to a dynamic-node-parameters endpoint and injects an absolute URL into the routing configuration. The n8n backend issues the outbound HTTP request to that URL from its own network context. Targets include cloud metadata services, internal management interfaces, and other private endpoints. Exploitation requires network access to the n8n instance, valid credentials, and a deployment where SSRF protection is disabled. Technical details are documented in the GitHub Security Advisory GHSA-9w78-79q7-r4fp and the VulnCheck SSRF Advisory.
Detection Methods for CVE-2026-65593
Indicators of Compromise
- Outbound HTTP requests from n8n server processes to internal RFC1918 addresses or cloud metadata endpoints such as 169.254.169.254
- Access logs showing calls to dynamic-node-parameters endpoints containing absolute URLs in routing fields
- Unexpected authenticated API calls originating from low-privilege n8n user accounts
Detection Strategies
- Inspect n8n application logs for requests to dynamic-node-parameters routes with URL parameters that differ from configured baseURL values
- Monitor egress traffic from n8n hosts for connections to internal address ranges not part of documented integrations
- Correlate authenticated session activity with anomalous outbound request patterns from the n8n host
Monitoring Recommendations
- Enable verbose HTTP request logging on n8n instances and forward logs to a centralized SIEM
- Alert on any requests from n8n to link-local, loopback, or private IP ranges
- Track invocations of dynamic-node-parameters endpoints per user account and flag unusual volume or destinations
How to Mitigate CVE-2026-65593
Immediate Actions Required
- Upgrade n8n to version 1.123.64 or later, which introduces authorization scopes on the affected endpoints
- Verify that SSRF protection is enabled in the n8n configuration and not overridden by environment variables
- Review authenticated user accounts and revoke access for any that are no longer required
- Restrict network egress from n8n hosts to only the destinations required by legitimate workflows
Patch Information
The fix is available in n8n version 1.123.64. Refer to the GitHub Security Advisory GHSA-9w78-79q7-r4fp for release notes and remediation details. Administrators running self-hosted deployments should apply the update promptly and validate that dynamic-node-parameters endpoints enforce authorization after upgrade.
Workarounds
- Ensure SSRF protection remains enabled by setting N8N_BLOCK_ENV_ACCESS_IN_NODE and related SSRF-related environment variables to secure values
- Place n8n behind a network egress proxy that denies traffic to internal IP ranges and cloud metadata endpoints
- Restrict access to the n8n API to trusted networks using firewall rules or a reverse proxy with IP allowlisting
- Limit authenticated user counts and enforce least-privilege role assignments until patching is complete
# Configuration example: enforce SSRF protection and egress restrictions
export N8N_SECURE_COOKIE=true
export N8N_BLOCK_ENV_ACCESS_IN_NODE=true
# Verify installed version meets or exceeds the patched release
npm list n8n | grep n8n
# Upgrade to the patched release
npm install -g n8n@1.123.64
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
