CVE-2026-27494: n8n has Arbitrary File Read via Python Code Node Sandbox Escape
Impact An authenticated user with permission to create or modify workflows could use the Python Code node to escape the sandbox. The sandbox did not sufficiently restrict access to certain built-in Python objects, allowing an attacker to exfiltrate file contents or achieve RCE.
On instances using internal Task Runners (default runner mode), this could result in full compromise of the n8n host. On instances using external Task Runners, the attacker might gain access to or impact other task executed on the Task Runner.
- Task Runners must be enabled using N8NRUNNERSENABLED=true.
Patches The issue has been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to this version 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 Code node by adding n8n-nodes-base.code 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.10.1, 2.9.3, and 1.123.22, an authenticated user with permission to create or modify workflows could use the Python Code node to escape the sandbox. The sandbox did not sufficiently restrict access to certain built-in Python objects, allowing an attacker to exfiltrate file contents or achieve RCE. On instances using internal Task Runners (default runner mode), this could result in full compromise of the n8n host. On instances using external Task Runners, the attacker might gain access to or impact other task executed on the Task Runner. Task Runners must be enabled using N8NRUNNERSENABLED=true. The issue has been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to this version 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 Code node by adding n8n-nodes-base.code to the NODESEXCLUDE environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
— NVD
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-27494?
CVE-2026-27494 is considered a high severity vulnerability due to the risk of remote code execution (RCE) and data exfiltration.
How do I fix CVE-2026-27494?
To remediate CVE-2026-27494, upgrade to n8n version 2.10.1, 2.9.3, or 1.123.22, depending on your currently installed version.
Who is affected by CVE-2026-27494?
CVE-2026-27494 affects authenticated users with permission to create or modify workflows in certain versions of n8n.
What are the potential impacts of CVE-2026-27494?
The impact of CVE-2026-27494 includes the ability to exfiltrate file contents and perform remote code execution from within the application.
What versions of n8n are vulnerable to CVE-2026-27494?
Versions of n8n between 2.0.0 and 2.9.3, and version 2.10.0 are vulnerable to CVE-2026-27494.