CVE-2026-27495: n8n has a Sandbox Escape in its JavaScript Task Runner
Impact An authenticated user with permission to create or modify workflows could exploit a vulnerability in the JavaScript Task Runner sandbox to execute arbitrary code outside the sandbox boundary.
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 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. - Use external runner mode (N8NRUNNERSMODE=external) to limit the blast radius.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Resources - n8n Documentation — Task Runners
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 exploit a vulnerability in the JavaScript Task Runner sandbox to execute arbitrary code outside the sandbox boundary. 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 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 use external runner mode (N8NRUNNERSMODE=external) to limit the blast radius. 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-27495?
CVE-2026-27495 has a high severity due to its potential for arbitrary code execution by authenticated users.
How do I fix CVE-2026-27495?
To fix CVE-2026-27495, upgrade n8n to version 2.10.1, 2.9.3, or 1.123.22 or later.
What types of users are affected by CVE-2026-27495?
Authenticated users with permissions to create or modify workflows are affected by CVE-2026-27495.
In which versions of n8n is CVE-2026-27495 present?
CVE-2026-27495 is present in n8n versions prior to 2.10.1, 2.9.3, and 1.123.22.
What is a potential impact of CVE-2026-27495?
The potential impact of CVE-2026-27495 includes executing arbitrary code outside the sandbox of the JavaScript Task Runner.