N8n, an open-source platform for workflow automation, has identified a critical security flaw. This vulnerability, tracked as CVE-2026-42232, allows authenticated users to potentially execute harmful code on affected systems. It’s a serious issue because it could let an attacker take control of your n8n instance.
The problem lies within the XML Node feature of n8n. An authenticated user who has permission to create or modify workflows could manipulate the XML Node to trigger a “prototype pollution” attack. When combined with other specific nodes, this pollution can then lead to Remote Code Execution (RCE). Essentially, this means an attacker could inject and run their own malicious code.
For organizations relying on n8n for their automation needs, understanding and addressing this vulnerability quickly is crucial to maintaining the security and integrity of their systems.
CVE Details
- Product Name: n8n
- Published: May 4, 2026
- Severity: HIGH (CVSS score 8.8)
- Status: Analyzed
Affected Products
This vulnerability impacts n8n instances running specific versions. If you are using any of the following, your system is vulnerable:
- n8n versions prior to 1.123.32
- n8n versions prior to 2.17.4
- n8n versions prior to 2.18.1
This includes both the standard and enterprise editions of the Node.js-based platform.
Current Status
The vulnerability (CVE-2026-42232) has been fully analyzed. This means the nature of the flaw is understood, and official patches have been released to address it. Users are strongly encouraged to act promptly to secure their installations.
Severity Level
The Common Vulnerability Scoring System (CVSS) rates this vulnerability with a score of 8.8 out of 10, classifying it as **HIGH** severity. This rating indicates that the flaw is easy to exploit over a network (Attack Vector: Network, Attack Complexity: Low) and requires only basic user privileges (Privileges Required: Low). No user interaction is needed for a successful attack (User Interaction: None). A successful exploit could lead to complete loss of confidentiality, integrity, and availability on the vulnerable system, and potentially high confidentiality and integrity impact on subsequent systems. This high score underscores the critical need for immediate action to mitigate the risk.
Possible Solutions
The good news is that n8n developers have already released patches to fix this vulnerability.
The primary solution is to **update your n8n installation** to one of the patched versions:
- n8n version 1.123.32 or later
- n8n version 2.17.4 or later
- n8n version 2.18.1 or later
Regularly updating your software is a fundamental cybersecurity practice, and this situation highlights its importance.
If an immediate upgrade isn’t feasible, there are temporary workarounds to consider:
- **Restrict permissions:** Limit the ability to create and edit workflows to only users who are fully trusted within your organization. This reduces the pool of potential attackers who could leverage this vulnerability.
- **Disable the XML Node:** You can disable the problematic XML node by adding
n8n-nodes-base.xmlto yourNODES_EXCLUDEenvironment variable. This prevents the specific vector of attack.
It is important to understand that these workarounds offer only partial protection and should only be used as a short-term measure. The best course of action is always to apply the official security updates as soon as possible.
References
https://github.com/n8n-io/n8n/security/advisories/GHSA-hqr4-h3xv-9m3r