CVE-2026-77083: n8n before 1.123.69 Code Node Sandbox Escape via Function.prototype Pollution
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 1.123.69 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.33.4 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.34.1
Event History
Frequently Asked Questions
Who can exploit this issue?
An attacker must be authenticated and able to create and execute workflows containing a JavaScript Code node. The full exploit chain also requires specific modules to be configured as allowlisted imports in the deployment.
Are all vulnerable n8n deployments equally exposed?
No. Although affected versions have the Code node sandbox weakness, successful exploitation additionally depends on the deployment allowing the specific modules needed by the exploit chain as imports.
What versions contain the fix?
The issue is fixed in n8n versions 1.123.69, 2.33.4, and 2.34.1. Versions earlier than those releases are affected.