p PatchFirst

CVE-2026-27495

CVE-2026-27495 · n8n has a Sandbox Escape in its JavaScript Task Runner

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 9.4 · Critical · EPSS 0.8% · Fix available

Published
Updated

Stack: node

Affected products and versions

  • n8n

    Versions
    • < 1.123.22: Affected
    • >= 2.0.0, < 2.9.3: Affected
    • >= 2.10.0, < 2.10.1: Affected

    No fix published

  • n8n npm

    Affected ranges
    • SEMVER: < 1.123.22

    Update to 1.123.22

  • n8n npm

    Affected ranges
    • SEMVER: ≥ 2.0.0, < 2.9.3

    Update to 2.9.3

  • n8n npm

    Affected ranges
    • SEMVER: ≥ 2.10.0, < 2.10.1

    Update to 2.10.1

Original sources

Check your server →