n8n before 1.123.69 Code Node Sandbox Escape via Function.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 is a workflow automation platform. In versions prior to 1.123.69, 2.33.4, and 2.34.1, the JavaScript Code node's VM sandbox did not freeze the sandbox's Function.prototype, allowing an authenticated user with the ability to create and execute workflows to pollute it from within a Code node execution and recover a reference to the host's globalThis, resulting in a sandbox escape. The full exploit chain additionally depends on specific modules being available as allowlisted imports in the deployment's configuration. The issue is fixed in versions 1.123.69, 2.33.4, and 2.34.1.
From the CVE record · VulnCheck
The JavaScript Code node’s VM sandbox does not freeze Function.prototype, allowing an authenticated user who can create and execute workflows to escape the sandbox. The full exploit chain also requires specific modules to be available as allowlisted imports in the deployment configuration.
Teams running n8n versions prior to 1.123.69, 2.33.4, or 2.34.1 should check their deployments.