n8n
Affected
- introduced
0, fixed1.123.76(semver)
Fixed versions
1.123.76
Fix
- Fixed version
1.123.76npm install [email protected]
Advisory
Also known as: CVE-2026-86083
n8n: Expression Sandbox Escape via Shared Builtin Tampering and Code-Printer Injection Leads to Code Execution
Impact
Two stages of expression code generation built source text by calling the global JSON.stringify at generation time: the compiler when printing synthetic string literals, and the isolate bridge when interpolating a timezone value into its per-evaluation wrapper. An expression that replaced that global therefore changed the code that was subsequently generated and executed, turning literal data into executable source. The patch renders both code-generation stages through a reference captured at module load, so a later change to global state cannot alter the generated source.
This vulnerability only affects instances running the legacy expression engine. The vm expression engine, which is the default on the patched releases, is not affected.
Patches
The issue has been fixed in n8n versions 1.123.76, 2.37.7, and 2.38.2. Users should upgrade to one of these versions or later to remediate the vulnerability.
Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
N8N_EXPRESSION_ENGINE=vm to switch to the vm expression engine, which is not affected by this vulnerability.These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
High Basis: The source's own band: HIGH
0, fixed 1.123.76 (semver)1.123.76
1.123.76npm install [email protected]2.38.0, fixed 2.38.2 (semver)2.38.2
2.38.2npm install [email protected]2.0.0, fixed 2.37.7 (semver)2.37.7
2.37.7npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0