CVE-2025-68613

Workarounds

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

• Limit workflow creation and editing permissions to fully trusted users only.
• Deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation.

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

n8n contains a critical Remote Code Execution (RCE) vulnerability in its workflow expression evaluation system. Under certain conditions, expressions supplied by authenticated users during workflow configuration may be evaluated in an execution context that is not sufficiently isolated from the underlying runtime.

An authenticated attacker could abuse this behavior to execute arbitrary code with the privileges of the n8n process. Successful exploitation may lead to full compromise of the affected instance, including unauthorized access to sensitive data, modification of workflows, and execution of system-level operations.

CVE-2025-68613 has a CVSS score of 9.9 (Critical). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.120.4, 1.121.1); upgrading removes the vulnerable code path.

Kodem intelligence

This issue has been fixed in n8n v1.122.0.

Users are strongly advised to upgrade to version 1.122.0 or later, which introduces additional safeguards to restrict expression evaluation.

1. What is CVE-2025-68613? CVE-2025-68613 is a critical-severity security vulnerability in n8n (npm), affecting versions >= 0.211.0, < 1.120.4. It is fixed in 1.120.4, 1.121.1.
2. How severe is CVE-2025-68613? CVE-2025-68613 has a CVSS score of 9.9 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of n8n are affected by CVE-2025-68613? n8n (npm) versions >= 0.211.0, < 1.120.4 is affected.
4. Is there a fix for CVE-2025-68613? Yes. CVE-2025-68613 is fixed in 1.120.4, 1.121.1. Upgrade to this version or later.
5. Is CVE-2025-68613 exploitable, and should I be worried? Whether CVE-2025-68613 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
6. What actually determines whether CVE-2025-68613 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.
7. How do I fix CVE-2025-68613?
   • Upgrade n8n to 1.120.4 or later
   • Upgrade n8n to 1.121.1 or later