UTC
High

JavaScript Task Runner VM Sandbox Escape via EventEmitter Prototype Pollution Leads to Remote Code Execution

GHSA-m3hg-p5r9-fg9h · published 2026-08-05

Severity
High
CVSS score
7.2
Chance of exploitation (EPSS)
No CVE
Fixed in
2.34.1
What it is

The JS task runner's prototype-freezing routine covered globalThis functions but not internal module constructors such as EventEmitter. An authenticated user with Code node access could exploit this gap to execute arbitrary commands within the runner container. Because the polluted prototype is a single process-wide object, the corruption persists across every other tenant's Code node execution subsequently scheduled on that same shared runner, but not on the host. On v1.x instances that have not enabled task runners, Code node JavaScript executes directly in the main n8n process instead, where the impact of a comparable sandbox escape could be significantly higher.

What to do

Upgrade n8n to 2.34.1 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

The issue has been fixed in n8n versions 1.123.69, 2.33.4, and 2.34.1. Users should upgrade to one of these versions or later to remediate the vulnerability.

If you cannot upgrade yet

If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Restrict n8n instance access to fully trusted users only. Disable Code node access for untrusted users. Run the JavaScript task runner in an isolated process per user or project where your deployment supports it. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Affected
PackageRegistryAffectedFixed in
n8nnpm< 1.123.691.123.69
n8nnpm< 2.33.42.33.4
n8nnpm< 2.34.12.34.1

The impact, patch and workaround text comes from the advisory, shortened (published by n8n). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].