GHSA-9CMH-XCQM-5HQR

n8n: Cross-Tenant Module-Cache Poisoning in the JS Task Runner

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

• Restrict n8n instance access to fully trusted users only.
• Disable built-in and external module access in Code nodes by unsetting NODE_FUNCTION_ALLOW_BUILTIN and NODE_FUNCTION_ALLOW_EXTERNAL, which removes the poisonable module surface.
• Use the external runner mode with a dedicated runner per user or project if your deployment supports it.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

n8n's JavaScript task runner shared one module cache across all users' Code-node executions, so a user able to run a Code node could poison a cached module and 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. It does not constitute a sandbox escape or remote code execution. All multi-user n8n instances running the JS task runner with built-in or external modules enabled are affected.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

Kodem intelligence

Already deployed Kodem?

The issue has been fixed in n8n versions 1.123.67, 2.31.5, and 2.32.1. Users should upgrade to one of these versions or later to remediate the vulnerability.

1. What is GHSA-9CMH-XCQM-5HQR? GHSA-9CMH-XCQM-5HQR is a medium-severity improper input validation vulnerability in n8n (npm), affecting versions < 1.123.67. It is fixed in 1.123.67, 2.32.1, 2.31.5. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. Which versions of n8n are affected by GHSA-9CMH-XCQM-5HQR? n8n (npm) versions < 1.123.67 is affected.
3. Is there a fix for GHSA-9CMH-XCQM-5HQR? Yes. GHSA-9CMH-XCQM-5HQR is fixed in 1.123.67, 2.32.1, 2.31.5. Upgrade to this version or later.
4. Is GHSA-9CMH-XCQM-5HQR exploitable, and should I be worried? Whether GHSA-9CMH-XCQM-5HQR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether GHSA-9CMH-XCQM-5HQR is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix GHSA-9CMH-XCQM-5HQR?
   • Upgrade n8n to 1.123.67 or later
   • Upgrade n8n to 2.32.1 or later
   • Upgrade n8n to 2.31.5 or later

Other vulnerabilities in n8n