Alex Joseph
Understanding the n8n Server-Side Request Forgery Vulnerability
A significant security flaw has been identified in n8n, an open-source workflow automation platform. This vulnerability, known as Server-Side Request Forgery (SSRF), could allow authenticated attackers to bypass security measures and potentially access internal systems. It’s crucial for users to understand this risk and take immediate action to secure their n8n instances.
CVE Details
Product Name: n8n
CVE ID: CVE-2026-65593
Published Date: July 22, 2026
Severity: Medium
Status: Analyzed
Affected Products
This vulnerability impacts specific versions of the n8n workflow automation platform. Both community and enterprise editions are affected if they are running:
- n8n versions before 1.123.64
- n8n versions before 2.29.8
- n8n versions before 2.30.1
Current Status
The vulnerability has been thoroughly analyzed, confirming its presence and potential impact. N8n has released patches to address this issue.
Severity Level
Rated as “Medium” severity, this SSRF vulnerability means that while an attacker needs to be authenticated to exploit it, the potential consequences can be serious. If successfully exploited, attackers could trick your n8n server into making unauthorized HTTP requests to internal networks. This could lead to information disclosure or access to other sensitive internal services that are not typically exposed to the internet.
Possible Solutions
The most effective way to protect your n8n instance from CVE-2026-65593 is to upgrade to a patched version immediately.
Patched Versions:
- n8n version 1.123.64 and later
- n8n version 2.29.8 and later
- n8n version 2.30.1 and later
Workarounds (Temporary Mitigations):
If an immediate upgrade isn’t possible, consider these temporary steps:
- Restrict User Access: Limit access to your n8n instance to only fully trusted users. Since exploitation requires authentication, this can reduce the attack surface.
- Enable SSRF Protection: Set the environment variable
N8N_SSRF_PROTECTION_ENABLED=true. This enables filtering for private IP ranges and cloud metadata endpoints, adding a layer of defense. Note that this setting is often disabled by default. - Network Egress Restrictions: Implement strict firewall rules to limit network outbound connections from the server hosting your n8n instance. This can help prevent the n8n server from reaching unauthorized internal services even if an SSRF attack occurs.
Please remember these workarounds only reduce the risk and do not fully resolve the vulnerability. Upgrading to the patched versions is strongly recommended for complete protection.
References
https://github.com/n8n-io/n8n/security/advisories/GHSA-9w78-79q7-r4fp
https://www.vulncheck.com/advisories/n8n-before-ssrf-via-dynamic-node-parameters
