Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to n8n instance
-
DeliveryCreate or modify workflow with XML/GSuiteAdmin node
-
ExploitSupply crafted parameters in node configuration
-
ExecutionPrototype pollution writes to Object.prototype
-
ImpactExecute arbitrary code on n8n instance
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A03:2021 - Injection
ASVS 5.0
V3 - Web Frontend Security Prototype pollution prevention
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Authenticated user with permission to create or modify workflows in n8n versions prior to 2.14.1, 2.13.3, or 1.123.27. Attacker crafts malicious parameters in XML or GSuiteAdmin node configuration to pollute Object.prototype and achieve RCE. |
| Impact | This vulnerability presents a high real-world risk despite requiring authentication. The CVSS 4.0 vector (AV:N/AC:L/PR:L) indicates network-accessible exploitation with low complexity and minimal privileges, making it straightforward to exploit once an attacker has basic authenticated access. The ability to achieve remote code execution elevates this from a theoretical concern to a critical operational risk, particularly in multi-tenant or shared n8n instances where workflow permissions may be broadly distributed. The impact scores (VC:H/VI:H/VA:H/SC:H/SI:H/SA:H) indicate complete compromise of confidentiality, integrity, and availability across both the vulnerable system and subsequent systems. While no EPSS score, KEV listing, or public POC is provided in the intelligence, the straightforward nature of prototype pollution exploitation in Node.js environments and the direct path to RCE suggest this vulnerability will be actively targeted once details become public. Organizations using n8n should treat this as an urgent patching priority, especially those with untrusted or semi-trusted users having workflow permissions. |
| Exploit ScenarioDerived | An authenticated attacker with workflow creation privileges logs into an n8n instance and creates a new workflow containing an XML or GSuiteAdmin node. The attacker crafts malicious node configuration parameters containing prototype pollution payloads (such as __proto__ or constructor.prototype property paths) that inject attacker-controlled values onto Object.prototype. When the workflow executes, the polluted prototype properties are leveraged by subsequent n8n operations to execute arbitrary code on the n8n server, granting the attacker full control over the instance and access to all workflow data, credentials, and connected systems. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 25, 2026
A prototype pollution vulnerability in the XML and GSuiteAdmin nodes of n8n workflow automation platform allows authenticated users with workflow creation or modification permissions to achieve remote code execution. Versions prior to 2.14.1, 2.13.3, and 1.123.27 are affected. The CVSS score of 9.4 (Critical) reflects network-based exploitation with low complexity requiring only low-level authentication, though no current KEV listing or public POC availability is indicated in the provided intelligence.
RemediationAI
Upgrade n8n to version 2.14.1, 2.13.3, or 1.123.27 or later immediately to fully remediate this vulnerability. Consult the official GitHub security advisory at https://github.com/n8n-io/n8n/security/advisories/GHSA-mxrg-77hm-89hv for version-specific upgrade guidance. If immediate patching is not feasible, implement temporary mitigations by restricting workflow creation and editing permissions exclusively to fully trusted users, and disable the XML node by adding n8n-nodes-base.xml to the NODES_EXCLUDE environment variable. Note that these workarounds provide only partial risk reduction and should be considered short-term measures only, as the GSuiteAdmin node remains a potential attack vector. Organizations should prioritize full version upgrades and conduct security reviews of existing workflows created by potentially untrusted users during the vulnerable period.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in npm, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability affects n8n (CPE: cpe:2.3:a:n8n-io:n8n), an open-source workflow automation platform built on Node.js. The issue stems from CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes, commonly known as Prototype Pollution), a JavaScript-specific vulnerability class where attackers can inject properties into Object.prototype. In this case, the XML and GSuiteAdmin nodes fail to properly validate or sanitize node configuration parameters, allowing crafted input to pollute the prototype chain. Because JavaScript property lookups traverse the prototype chain, pollution of Object.prototype affects all objects in the runtime, enabling attackers to override critical properties and achieve code execution through subsequent operations that rely on these polluted values.
Know when N8n gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
3DescriptionGitHub Advisory
n8n is an open source workflow automation platform. Prior to versions 2.14.1, 2.13.3, and 1.123.27, an authenticated user with permission to create or modify workflows could exploit a prototype pollution vulnerability in the XML and the GSuiteAdmin nodes. By supplying a crafted parameters as part of node configuration, an attacker could write attacker-controlled values onto Object.prototype. An attacker could use this prototype pollution to achieve remote code execution on the n8n instance. The issue has been fixed in n8n versions 2.14.1, 2.13.3, and 1.123.27. Users should upgrade to one of these versions or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only, and/or disable the XML node by adding n8n-nodes-base.xml to the NODES_EXCLUDE environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Articles & Coverage 2
Executive ViewAI
A critical vulnerability in n8n workflow automation platform allows authenticated users to execute arbitrary code, potentially compromising all systems and data accessible through affected instances. Organizations using n8n versions prior to 2.14.1, 2.13.3, or 1.123.27 face immediate risk of data breach, system compromise, and operational disruption, particularly if workflows interact with sensitive business processes or connected systems.
Disable XML and GSuiteAdmin nodes in workflow templates until patching is complete; restrict n8n instance network access to authorized internal networks only via firewall rules; implement strict role-based access controls limiting workflow creation/modification to trusted administrators; monitor workflow execution logs for anomalous behavior; consider air-gapping critical n8n instances from production systems. These controls reduce but do not eliminate risk—patching is mandatory.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Related Vulnerabilities in n8n Workflow Automation Security Flaws
View all 3Remote code execution in n8n's workflow expression evaluation system allows an authenticated user with workflow creation
n8n workflow automation (through 1.121.2) allows authenticated users to execute arbitrary code via the n8n service, with
n8n workflow automation (1.65.0 to 1.121.0) allows unauthenticated file access through form-based workflows. A critical
n8n has a fifth critical RCE vulnerability (CVSS 9.9) in the Expression evaluator, enabling code execution through craft
Authenticated users who can create or modify an n8n workflow can achieve remote code execution on the n8n host by abusin
n8n-workflows Main Commit ee25413 allows attackers to execute a directory traversal via the download_workflow function w
Authenticated n8n users can hijack administrator accounts when LDAP authentication is enabled by manipulating their LDAP
The n8n package 0.218.0 for Node.js allows Escalation of Privileges. Rated high severity (CVSS 8.8), this vulnerability
SQL injection in n8n's Data Table Get node allows authenticated users with workflow modification permissions to execute
Authenticated users can exploit string formatting and exception handling in n8n's Python task executor to escape sandbox
EUVD-2026-15945
GHSA-mxrg-77hm-89hv
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB