Understanding the n8n Denial of Service Vulnerability
A significant security flaw has been identified in n8n, an open-source workflow automation platform. This vulnerability, tracked as CVE-2026-42236, could allow an unauthorized attacker to disrupt your n8n services, making your automation workflows inaccessible. It’s a serious issue because it doesn’t require any special access or authentication for an attacker to exploit it.
The problem lies within n8n’s MCP OAuth client registration endpoint. This part of the system allowed requests from anyone without verifying their identity. Crucially, it also stored client data without proper limits on how much information it could handle. This oversight means a malicious actor could send a very large amount of registration data, quickly filling up the server’s memory and causing the entire n8n instance to crash. This endpoint was reachable even if the MCP access was disabled, making the vulnerability more widespread than it might initially appear.
CVE Details
- Product: n8n
- Published Date: May 4, 2026
- Severity: High (CVSS v3.1: 7.5, CVSS v4.0: 8.7)
- Status: Analyzed
Affected Products
This vulnerability impacts specific versions of the n8n workflow automation platform. If you are running any n8n version prior to the following, your instance is at risk:
- n8n versions before 1.123.32
- n8n versions before 2.17.4
- n8n versions before 2.18.1
It’s crucial to identify your current n8n version and compare it against these patched versions.
Current Status
The vulnerability, CVE-2026-42236, has been officially Analyzed. This means the details of the vulnerability, its impact, and potential solutions have been thoroughly investigated and confirmed by security researchers and the n8n development team. The information is public, and patches are available.
Severity Level
This vulnerability is classified as High Severity, with a CVSS v3.1 score of 7.5 and a CVSS v4.0 score of 8.7. This high rating reflects several critical factors:
- Ease of Exploitation: An attacker doesn’t need to be authenticated, meaning they don’t need a username or password to launch an attack.
- Low Attack Complexity: The attack itself is straightforward and doesn’t require advanced techniques or specific conditions.
- Significant Impact: Successful exploitation leads to a denial of service, rendering the n8n platform completely unavailable. For organizations relying on n8n for critical automated workflows, this can cause significant operational disruption and financial losses.
Possible Solutions
The n8n development team has released patches to address this critical vulnerability. To secure your n8n instance, it is highly recommended to:
- Upgrade Immediately: Update your n8n installation to version 1.123.32, 2.17.4, 2.18.1, or later. These versions contain the necessary fixes to prevent unauthenticated denial of service attacks.
Temporary Workarounds (Use with caution)
If an immediate upgrade isn’t feasible, consider these temporary mitigation steps. Please note that these do not fully resolve the vulnerability and should only be used as short-term measures while you prepare for a full upgrade:
- Restrict Network Access: Limit who can access your n8n instance over the network. Only allow trusted IP addresses or internal networks to reach the n8n server.
- Adjust Payload Size: Reduce the maximum accepted payload size for requests by setting the
N8N_PAYLOAD_SIZE_MAXenvironment variable to a lower value than its default. This might help prevent large, malicious payloads from exhausting resources.
References
- https://github.com/n8n-io/n8n/security/advisories/GHSA-49m9-pgww-9vq6