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-86076
n8n: Expression Sandbox Escape via Class-Field Sanitizer Rebinding Can Lead to Code Execution
Impact
The expression compiler's sanitizer resolved through a dynamically-scoped this, so a class field named __sanitize rebound it and reached the Function constructor. On the backend, any expression author could run code in the n8n process; in the editor preview, a member's expression could run as JavaScript in the session of whoever opened the workflow. The patch rejects reserved class-member names.
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.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