n8n's JavaScript task runner shared a single module cache across all users' Code-node executions. In affected versions (before 1.123.67, 2.31.5, and 2.32.1), a user able to run a Code node could poison a cached module and thereby alter other users' Code-node executions on the same runner, affecting their confidentiality, integrity, or availability. This is a cross-user isolation break within a single n8n instance and does not constitute a sandbox escape or remote code execution. Only multi-user instances running the JS task runner with built-in or external modules enabled are affected.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/n8n-io/n8n/security/advisories/GHSA-9cmh-xcqm-5hqr Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.8 · n8nNVD modified 2026-10-23 19:10
Affected (CPE criteria) 2
cpe:2.3:a:n8n:n8n:*:*:*:*:*:node.js:*:*cpe:2.3:a:n8n:n8n:2.32.0:*:*:*:*:node.js:*:*
References 2
- https://github.com/n8n-io/n8n/security/advisories/GHSA-9cmh-xcqm-5hqr Mitigation, Vendor Advisory
- https://www.vulncheck.com/advisories/n8n-before-module-cache-poisoning-via-code-node Third Party Advisory