n8n has a Sandbox Escape in its JavaScript Task Runner

Summary

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 `N8N_RUNNERS_ENABLED=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 (`N8N_RUNNERS_MODE=external`) to limit the blast radius. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Timeline

1. Feb 25, 2026, 10:10 PM UTCCVE published
2. Feb 26, 2026, 8:28 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Feb 26, 2026, 8:28 PM UTCRecord last updated

Affected versions

• n8n-io n8n

  fixed in 1.123.22; From 2.0.0 · fixed in 2.9.3; From 2.10.0 · fixed in 2.10.1

• n8nnpm

  fixed in 1.123.22

• n8nnpm

  From 2.0.0 · fixed in 2.9.3

• n8nnpm

  From 2.10.0 · fixed in 2.10.1

References 6