The vulnerability identified as CVE-2026-33696 in the n8n open source workflow automation platform is a prototype pollution flaw classified under CWE-1321. It affects multiple versions of n8n prior to 2.14.1, 2.13.3, and 1.123.27. The issue arises in the XML and GSuiteAdmin nodes where an authenticated user with permissions to create or modify workflows can supply maliciously crafted parameters during node configuration. These parameters allow the attacker to write arbitrary values onto the JavaScript Object.prototype, a fundamental object from which all other objects inherit properties. By polluting the prototype, the attacker can alter the behavior of the application globally, potentially leading to remote code execution (RCE) on the n8n server instance. This RCE can be achieved without user interaction and requires only low privileges (authenticated user with workflow modification rights). The vulnerability is severe due to the combination of ease of exploitation, the critical nature of RCE, and the broad impact on confidentiality, integrity, and availability of the affected system. The issue was publicly disclosed on March 25, 2026, with a CVSS 4.0 base score of 9.4, reflecting its critical severity. The vendor has released fixed versions 2.14.1, 2.13.3, and 1.123.27 to remediate the vulnerability. Until upgrading is possible, temporary mitigations include limiting workflow creation and editing permissions to fully trusted users and disabling the XML node by excluding it via the NODES_EXCLUDE environment variable. However, these mitigations do not fully resolve the risk and should only be considered short-term measures.

The impact of CVE-2026-33696 is significant for organizations using n8n as it allows an authenticated user with relatively low privileges to execute arbitrary code remotely on the server hosting the workflow automation platform. This can lead to full system compromise, data theft, unauthorized access to sensitive workflows and data, disruption of automated business processes, and potential lateral movement within the network. Given n8n’s role in automating workflows that may integrate with various enterprise systems and cloud services, exploitation could cascade into broader organizational impacts including data breaches, operational downtime, and reputational damage. The vulnerability’s ease of exploitation and lack of user interaction requirements increase the risk of rapid exploitation once discovered. Organizations relying on n8n for critical automation should consider this a high-priority threat.

To mitigate CVE-2026-33696, organizations should immediately upgrade n8n to versions 2.14.1, 2.13.3, or 1.123.27 or later, where the vulnerability is patched. If upgrading is not feasible immediately, restrict workflow creation and modification permissions strictly to fully trusted and vetted users to reduce the attack surface. Additionally, disable the XML node by adding 'n8n-nodes-base.xml' to the NODES_EXCLUDE environment variable to prevent exploitation via this vector. Regularly audit user permissions and monitor workflow changes for suspicious activity. Implement network segmentation and access controls to limit exposure of the n8n instance. Employ runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to detect anomalous behavior indicative of exploitation attempts. Finally, maintain up-to-date backups and incident response plans to recover quickly if compromise occurs.