CVE Intelligence
Analysis AI-assisted

CVE-2026-27495: n8n JavaScript Task Runner Sandbox Escape (CWE-94)

Authenticated users who can create or modify workflows in affected n8n releases may be able to escape the JavaScript Task Runner sandbox and run code outside its boundary. The sources describe possible full compromise of the n8n host when internal runners are used, and possible impact on other tasks when external runners are used. Upgrading to a fixed release is the primary remediation, and the affected ranges are detailed in the body.

Published Oct 24, 2026 · Updated Oct 24, 2026 · Ler em português

Overview

n8n is an open source workflow automation platform. This record describes a sandbox escape in its JavaScript Task Runner, classified as code injection (CWE-94). Per the advisory text, a user who can create or modify workflows may run code outside the intended sandbox boundary.

Impact

  • On instances using internal Task Runners (the default runner mode), the sources describe possible full compromise of the n8n host.
  • On instances using external Task Runners, an attacker might gain access to or affect other tasks executed on the runner.
  • The NVD base score is 9.9 (critical), with network attack vector, low privileges required, no user interaction, and high confidentiality, integrity and availability impact. A GitHub CNA score of 9.4 is also recorded, without its vector string in the record.

Affected products and versions

The record lists two product entries, N8n N8n and N8n-io N8n, with the same ranges:

  • Before 1.123.22.
  • From 2.0.0 up to but not including 2.9.3.
  • From 2.10.0 up to but not including 2.10.1.

The advisory states the issue is fixed in 2.10.1, 2.9.3 and 1.123.22. Task Runners must be enabled with N8N_RUNNERS_ENABLED=true for the issue to apply, as stated in the record.

Exploitation status

The record shows that this CVE is not listed in CISA KEV, that the SSVC exploitation field is none, and that the EPSS probability is 0.0092. No confirmed exploitation appears in the sources consulted.

Remediation and mitigation

  • Upgrade to 2.10.1, 2.9.3, 1.123.22 or a later release, as applicable to your branch.
  • If upgrading is not immediately possible, restrict workflow creation and editing to fully trusted users only.
  • Consider external runner mode (N8N_RUNNERS_MODE=external) to limit the blast radius. The advisory states these workarounds do not fully remediate the risk and should be short-term only.
  • Confirm whether Task Runners are enabled in your deployment, since the issue depends on that setting.

Detection guidance

  • Review recent audit or activity records for workflow creation and modification, especially changes by low-privileged or unexpected accounts.
  • Monitor the n8n host for unexpected process or network activity originating from the n8n service account.
  • Review runner-related logs for anomalous behavior in external runner setups.

Limitations of the available information

  • The record's fixes field is empty, although the description names the fixed versions. Verify against the vendor advisory before acting.
  • The record does not describe the technical details of the sandbox weakness, and no technical write-up is among the cited references. This analysis does not include such details.
  • The GitHub CNA CVSS vector is not included in the record.
  • Exploitation likelihood is based only on the KEV, SSVC and EPSS fields provided; it may change as more information becomes available.

Frequently asked questions

Which n8n versions are affected by CVE-2026-27495?

According to the record, affected ranges are before 1.123.22, from 2.0.0 up to but not including 2.9.3, and from 2.10.0 up to but not including 2.10.1.

Which versions fix this issue?

The advisory text states the issue is fixed in 2.10.1, 2.9.3 and 1.123.22. Upgrade to one of these or a later release.

Is this vulnerability being actively exploited?

The record does not list it in CISA KEV, and no confirmed exploitation appears in the sources consulted.

Does this affect every n8n deployment?

The description says the issue depends on Task Runners being enabled with N8N_RUNNERS_ENABLED=true. Impact differs between internal and external runner modes.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.