CVE-2026-72764: n8n before 1.123.67 Module Cache Poisoning via Code Node
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.
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.67 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.31.5 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.32.1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-72764?
CVE-2026-72764 has a risk rating of 44, indicating a moderate severity vulnerability.
How do I fix CVE-2026-72764?
To fix CVE-2026-72764, upgrade to n8n version 1.123.67, 2.31.5, or 2.32.1 or later.
What is CVE-2026-72764 about?
CVE-2026-72764 describes a module cache poisoning vulnerability in n8n's Code node that could impact multiple users.
Who is affected by CVE-2026-72764?
Any user running n8n versions before 1.123.67, 2.31.5, or 2.32.1 is affected by CVE-2026-72764.
How does CVE-2026-72764 impact n8n users?
CVE-2026-72764 allows a user to manipulate the module cache, potentially affecting other users' Code-node executions.