CVE-2026-33696: n8n Vulnerable to Prototype Pollution in XML & GSuiteAdmin node parameters lead to RCE
Impact An authenticated user with permission to create or modify workflows could exploit a prototype pollution vulnerability in the GSuiteAdmin node. By supplying a crafted parameter 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.
Patches 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.
Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Limit workflow creation and editing permissions to fully trusted users only. - Disable the XML node by adding n8n-nodes-base.xml to the NODESEXCLUDE environment variable.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Other sources
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 NODESEXCLUDE environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 1.123.27 - Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.13.3 - Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.14.1 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.14.1 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.13.3 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 1.123.27 - Configuration
Temporarily disable the XML node by adding `n8n-nodes-base.xml` to the `NODES_EXCLUDE` environment variable.
n8n (environment configuration) NODES_EXCLUDE (add node to exclude list) = n8n-nodes-base.xml - Compensating control
Temporarily mitigate by limiting workflow creation and editing permissions to fully trusted users only.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-33696?
The severity of CVE-2026-33696 is high due to the potential for remote code execution through prototype pollution.
How do I fix CVE-2026-33696?
To fix CVE-2026-33696, upgrade n8n to versions 2.14.1, 2.13.3, or 1.123.27 or later.
What types of users are affected by CVE-2026-33696?
Authenticated users with permission to create or modify workflows are affected by CVE-2026-33696.
What is prototype pollution as related to CVE-2026-33696?
Prototype pollution in CVE-2026-33696 refers to the manipulation of an object's prototype, which can lead to unexpected behavior and vulnerabilities.
What versions of n8n are vulnerable to CVE-2026-33696?
Versions of n8n prior to 2.14.1, 2.13.3, and 1.123.27 are vulnerable to CVE-2026-33696.