CVE-2025-68613: CWE-913: Improper Control of Dynamically-Managed Code Resources in 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.
AI Analysis
Technical Summary
The vulnerability identified as CVE-2025-68613 affects the n8n open source workflow automation platform, specifically versions starting from 0.211.0 up to 1.120.4 and version 1.121.0. The root cause is an improper control of dynamically-managed code resources (CWE-913) within the workflow expression evaluation system. When workflows are configured, expressions supplied by authenticated users are evaluated in a runtime context that lacks sufficient isolation. This flaw allows an attacker with authenticated access to inject and execute arbitrary code with the same privileges as the n8n process. Because n8n often runs with significant system privileges to automate workflows, successful exploitation can lead to complete compromise of the host environment. Attackers could access sensitive data, alter or create malicious workflows, and perform system-level operations such as installing malware or pivoting within the network. The vulnerability does not require user interaction beyond authentication, making it easier to exploit once credentials are obtained. The vendor has released patched versions (1.120.4, 1.121.1, and 1.122.0) that introduce enhanced safeguards to restrict expression evaluation contexts and prevent code injection. Until upgrades are applied, administrators are advised to limit workflow editing permissions strictly to trusted users and run n8n in hardened environments with minimal privileges and network restrictions. Although no known exploits in the wild have been reported yet, the critical nature and ease of exploitation make this a high-risk vulnerability.
Potential Impact
For European organizations, the impact of this vulnerability is significant due to the potential for full system compromise. n8n is used by enterprises for automating business-critical workflows, often integrating with sensitive data sources and internal systems. Exploitation could lead to unauthorized disclosure of confidential information, disruption of automated processes, and unauthorized changes to workflows that could propagate malicious actions across connected systems. The ability to execute arbitrary code at the system level increases the risk of ransomware deployment, lateral movement, and persistent backdoors. Organizations in sectors such as finance, healthcare, manufacturing, and public administration, where automation platforms like n8n are increasingly adopted, face heightened risks. The vulnerability’s requirement for authenticated access means that credential compromise or insider threats could trigger exploitation. Given the critical CVSS score and the broad impact on confidentiality, integrity, and availability, European entities must prioritize remediation to prevent potential operational and reputational damage.
Mitigation Recommendations
1. Immediate upgrade to n8n versions 1.120.4, 1.121.1, or 1.122.0 to apply the official patches that address the vulnerability. 2. Restrict workflow creation and editing permissions exclusively to fully trusted and vetted users to reduce the attack surface. 3. Deploy n8n instances within hardened environments: run with the least privilege principle, using dedicated service accounts with minimal OS permissions. 4. Isolate n8n servers in segmented network zones with strict firewall rules to limit exposure and lateral movement in case of compromise. 5. Implement strong authentication mechanisms, including multi-factor authentication (MFA), to reduce the risk of credential theft leading to exploitation. 6. Monitor logs and workflow changes for suspicious activity indicative of exploitation attempts or unauthorized modifications. 7. Conduct regular security audits and penetration testing focused on workflow automation platforms to identify potential misconfigurations or vulnerabilities. 8. If immediate patching is not feasible, consider disabling or limiting access to the expression evaluation features or workflows that accept user-supplied expressions. These measures should be temporary and replaced by patching as soon as possible.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Italy, Spain, Belgium, Poland, Ireland
CVE-2025-68613: CWE-913: Improper Control of Dynamically-Managed Code Resources in n8n-io n8n
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.
AI-Powered Analysis
Technical Analysis
The vulnerability identified as CVE-2025-68613 affects the n8n open source workflow automation platform, specifically versions starting from 0.211.0 up to 1.120.4 and version 1.121.0. The root cause is an improper control of dynamically-managed code resources (CWE-913) within the workflow expression evaluation system. When workflows are configured, expressions supplied by authenticated users are evaluated in a runtime context that lacks sufficient isolation. This flaw allows an attacker with authenticated access to inject and execute arbitrary code with the same privileges as the n8n process. Because n8n often runs with significant system privileges to automate workflows, successful exploitation can lead to complete compromise of the host environment. Attackers could access sensitive data, alter or create malicious workflows, and perform system-level operations such as installing malware or pivoting within the network. The vulnerability does not require user interaction beyond authentication, making it easier to exploit once credentials are obtained. The vendor has released patched versions (1.120.4, 1.121.1, and 1.122.0) that introduce enhanced safeguards to restrict expression evaluation contexts and prevent code injection. Until upgrades are applied, administrators are advised to limit workflow editing permissions strictly to trusted users and run n8n in hardened environments with minimal privileges and network restrictions. Although no known exploits in the wild have been reported yet, the critical nature and ease of exploitation make this a high-risk vulnerability.
Potential Impact
For European organizations, the impact of this vulnerability is significant due to the potential for full system compromise. n8n is used by enterprises for automating business-critical workflows, often integrating with sensitive data sources and internal systems. Exploitation could lead to unauthorized disclosure of confidential information, disruption of automated processes, and unauthorized changes to workflows that could propagate malicious actions across connected systems. The ability to execute arbitrary code at the system level increases the risk of ransomware deployment, lateral movement, and persistent backdoors. Organizations in sectors such as finance, healthcare, manufacturing, and public administration, where automation platforms like n8n are increasingly adopted, face heightened risks. The vulnerability’s requirement for authenticated access means that credential compromise or insider threats could trigger exploitation. Given the critical CVSS score and the broad impact on confidentiality, integrity, and availability, European entities must prioritize remediation to prevent potential operational and reputational damage.
Mitigation Recommendations
1. Immediate upgrade to n8n versions 1.120.4, 1.121.1, or 1.122.0 to apply the official patches that address the vulnerability. 2. Restrict workflow creation and editing permissions exclusively to fully trusted and vetted users to reduce the attack surface. 3. Deploy n8n instances within hardened environments: run with the least privilege principle, using dedicated service accounts with minimal OS permissions. 4. Isolate n8n servers in segmented network zones with strict firewall rules to limit exposure and lateral movement in case of compromise. 5. Implement strong authentication mechanisms, including multi-factor authentication (MFA), to reduce the risk of credential theft leading to exploitation. 6. Monitor logs and workflow changes for suspicious activity indicative of exploitation attempts or unauthorized modifications. 7. Conduct regular security audits and penetration testing focused on workflow automation platforms to identify potential misconfigurations or vulnerabilities. 8. If immediate patching is not feasible, consider disabling or limiting access to the expression evaluation features or workflows that accept user-supplied expressions. These measures should be temporary and replaced by patching as soon as possible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-12-19T14:58:47.823Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6945d4648954746f284878c5
Added to database: 12/19/2025, 10:40:36 PM
Last enriched: 12/27/2025, 4:28:27 AM
Last updated: 2/6/2026, 7:56:11 PM
Views: 769
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-2064: Cross Site Scripting in Portabilis i-Educar
MediumCVE-2026-25727: CWE-121: Stack-based Buffer Overflow in time-rs time
MediumCVE-2026-25643: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in blakeblackshear frigate
CriticalCVE-2026-1709: Key Exchange without Entity Authentication in Red Hat Red Hat Enterprise Linux 10
CriticalCVE-2025-15320: Multiple Binds to the Same Port in Tanium Tanium Client
LowActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.