Sovra Recon·Actively exploited

CVE-2025-68613n8n Improper Control of Dynamically-Managed Code Resources Vulnerability

At a glance

CVE-2025-68613 is a critical-severity vulnerability (CVSS score 9.9) affecting n8n (n8n). CISA has confirmed that attackers have been exploiting it since March 11, 2026.

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.

Details

The vulnerability in detail

CVE ID
CVE-2025-68613
Vendor
n8n
Product
n8n
Severity (CVSS)
Critical · 9.9 / 10
Published
December 20, 2025
Actively exploited
Yes, confirmed by CISA on March 11, 2026
Used in ransomware
Not reported
Weakness type (CWE)
CWE-913

What to do

How to protect against CVE-2025-68613

  • Check whether you are affected: identify the installed versions of the product and compare them with the vendor's security advisory.
  • Apply the vendor's patch as a priority on Internet-facing systems, since this vulnerability is already being exploited.
  • If no patch is available, apply the published workarounds or take the service off the Internet.
  • Look for signs of compromise: a vulnerability exploited before you patched may already have been used. Review your logs and the indicators published by the vendor.

Sources

Official descriptions from NVD and CISA, in their original wording.

Patching a CVE is not enough.

The vulnerabilities specific to your application have no CVE. Our AI agents hunt for them by actually attacking your systems.