criticalCVSS 9.9exploited in the wild (CISA KEV)NVD status: Analyzed

CVE-2025-68613

n8n is an open source workflow automation platform.

Componentn8n
Severitycritical (CVSS 9.9)
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Published (NVD)2025-12-19
Last modified2026-10-13
Affected versions
n8n >= 0.211.0, < 1.120.4
n8n = 1.121.0
Fixed in1.120.4
WeaknessCWE-913
CISA KEVlisted 2026-03-11

NVD description

n8n is an open source workflow automation platform. Versions starting with 0.211.0 and prior to 1.120.4, 1.121.1, and 1.122.0 contain a critical Remote Code Execution (RCE) vulnerability in their 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. This issue has been fixed in versions 1.120.4, 1.121.1, and 1.122.0. Users are strongly advised to upgrade to a patched version, which introduces additional safeguards to restrict expression evaluation. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only; and/or 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.

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Does CVE-2025-68613 hit the version you run?Paste your docker-compose.yml, requirements.txt or package.json. The scanner checks your pinned versions against this CVE and every other one we track for n8n.
Check my stack

What to do

  • Upgrade n8n to 1.120.4 or later.
  • Do not expose the component's API or UI to the internet without authentication in front of it.
  • It is exploited in the wild: treat unpatched hosts as compromised, rotate the secrets they hold and review their logs.

Sources

Read more

Other n8n CVEs

All n8n CVEs