n8n Improper Control of Dynamically-Managed Code Resources Vulnerability
n8n-io — n8n
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.
10.0
97.9%
Vector breakdown
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- Published
- Dec 19, 2025
- Modified
- Mar 12, 2026
- Added to KEV
- Mar 11, 2026
- Federal patch due
- Mar 25, 2026
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.
Weakness classification
Proof-of-concept & exploitation references
Weaponization
Public repositories whose name or description references CVE-2025-68613, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit - cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.
No public GitHub repositories referencing CVE-2025-68613 were found at last check. Absence here is not proof no exploit exists - see the references below for vendor advisories and write-ups.
References
Frequently asked questions
What is CVE-2025-68613?
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.
How severe is CVE-2025-68613?
CVE-2025-68613 has a CVSS base score of 10.0 out of 10 (CVSS 3.1).
Is CVE-2025-68613 actively exploited in the wild?
Yes. CVE-2025-68613 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Mar 11, 2026, meaning CISA has confirmed evidence of active exploitation.
What is the EPSS score for CVE-2025-68613?
97.9% - meaning FIRST.org's EPSS model estimates a 97.9% probability this vulnerability will be exploited in the wild within 30 days (100% percentile among all scored CVEs).
Is there exploit tooling available for CVE-2025-68613?
Yes - a public Nuclei template referencing CVE-2025-68613 exist in public repositories we checked.
What type of vulnerability is CVE-2025-68613?
CVE-2025-68613 is classified under CWE-913 (CWE-913: Improper Control of Dynamically-Managed Code Resources).
Cross-checked against
Impactr finds and proves whether CVE-2025-68613 - or flaws like it - are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.
Join the waitlist