n8n before 1.123.69 Remote Code Execution via EventEmitter Prototype Pollution
n8n-io n8n
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
n8n-io n8n
| Product | Affected | Fixed in |
|---|---|---|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
n8n versions before 1.123.69, 2.33.4, and 2.34.1 contain a JavaScript task runner VM sandbox escape. The runner's prototype-freezing routine covers globalThis functions but not internal module constructors such as EventEmitter, allowing an authenticated user with Code node access to exploit prototype pollution to execute arbitrary commands within the runner container. Because the polluted prototype is a process-wide object, the corruption persists across other tenants' Code node executions on the same shared runner. On v1.x instances without task runners enabled, Code node JavaScript runs directly in the main n8n process, where the impact could be higher.
From the CVE record · VulnCheck
n8n’s JavaScript task runner VM sandbox does not freeze certain internal module constructors, allowing prototype pollution. An authenticated user with Code node access can escape the sandbox and execute arbitrary commands in the runner container; the pollution can persist across other tenants’ Code node executions on a shared runner. On v1.x instances without task runners enabled, Code node JavaScript runs in the main n8n process, where the impact could be higher.
Operators of n8n versions before 1.123.69, 2.33.4, or 2.34.1 should check their installations.