CVE-2026-27494

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 NODES_EXCLUDE environment variable.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

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 N8N_RUNNERS_ENABLED=true.

CVE-2026-27494 has a CVSS score of 9.9 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.123.22, 2.9.3, 2.10.1); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2026-27494? CVE-2026-27494 is a high-severity security vulnerability in n8n (npm), affecting versions < 1.123.22. It is fixed in 1.123.22, 2.9.3, 2.10.1.
2. How severe is CVE-2026-27494? CVE-2026-27494 has a CVSS score of 9.9 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of n8n are affected by CVE-2026-27494? n8n (npm) versions < 1.123.22 is affected.
4. Is there a fix for CVE-2026-27494? Yes. CVE-2026-27494 is fixed in 1.123.22, 2.9.3, 2.10.1. Upgrade to this version or later.
5. Is CVE-2026-27494 exploitable, and should I be worried? Whether CVE-2026-27494 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-27494 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-27494?
   • Upgrade n8n to 1.123.22 or later
   • Upgrade n8n to 2.9.3 or later
   • Upgrade n8n to 2.10.1 or later