n8n Workflow Expression Evaluation Remote Code Execution (RCE) Vulnerability Advisory (CVE-2025-68613)
Executive & SecOps Summary
SECOPS ASSESSMENTn8n versions starting with 0.211.0 and prior to 1.120.4, 1.121.1, and 1.122.0
Authenticated attackers can exploit an insufficiently isolated execution context during expression evaluation to execute arbitrary system commands with n8n process privileges, potentially leading to full instance compromise
Immediately upgrade n8n to patched versions (1.120.4, 1.121.1, or 1.122.0 and above)
Affected Products & Version Scope
Remediation & Live Workaround Commands
PATCH & WORKAROUND1. Official Patch & Version Upgrade Commands
Immediately upgrade your n8n instances to the patched versions (1.120.4, 1.121.1, or 1.122.0 and above). For Docker-based deployments, update your image tag and recreate the container as shown below:
# Update n8n image tag in docker-compose.yml to a secure version (e.g., 1.122.0)
sed -i 's/n8nio\/n8n:.*/n8nio\/n8n:1.122.0/g' docker-compose.yml
# Pull the secure image and recreate the container
docker-compose down
docker-compose pull
docker-compose up -d2. Temporary Workaround & Hardening Configuration
If an immediate upgrade is not feasible, apply the following temporary mitigations to reduce the attack surface:
- Restrict Permissions: Limit workflow creation and editing privileges to highly trusted administrators only.
- Container Hardening: Run the n8n container as a non-root user and restrict its operating system privileges.
- Network Isolation: Restrict outbound network access from the n8n container to prevent reverse shells and external payload downloads.
# Example: Restrict outbound traffic from the n8n container (assuming container IP is 172.18.0.5)
# Block all outbound traffic except to authorized internal services
iptables -A FORWARD -s 172.18.0.5 -p tcp --dport 80 -j REJECT
iptables -A FORWARD -s 172.18.0.5 -p tcp --dport 443 -m state --state NEW -j REJECT3. Log Audit & IoC Verification Commands
Audit your n8n logs and container processes for suspicious child process spawning. Use the following script to verify the running n8n version and check if it is vulnerable:
# Script to check running n8n container version and vulnerability status
CONTAINER_ID=$(docker ps -q --filter ancestor=n8nio/n8n)
if [ -n '$CONTAINER_ID' ]; then
CURRENT_VER=$(docker exec -it $CONTAINER_ID n8n --version | tr -d '\r')
echo '[+] Current n8n Version: '$CURRENT_VER
if [[ '$CURRENT_VER' =~ ^0\. || '$CURRENT_VER' =~ ^1\.(1[0-9]|120\.[0-3]|121\.0)$ ]]; then
echo '[!] WARNING: This version is VULNERABLE to CVE-2025-68613. Immediate patch required.'
else
echo '[+] Status: Safe or patched version.'
fi
else
echo '[-] No running n8n container found.'
fiScan Your Repositories for Transitive Vulnerable Dependencies in 30 Seconds
Automatically detect vulnerable packages across npm, PyPI, Maven, and Go, and open automated fix Pull Requests without breaking your build.
Technical Root Cause & Exploitation Mechanics
1. Vulnerability Overview & Root Cause
This vulnerability (CVE-2025-68613) is a critical Remote Code Execution (RCE) flaw residing in the workflow expression evaluation engine of n8n, an open-source workflow automation platform. n8n allows users to write JavaScript-like expressions to manipulate data dynamically within workflows. However, in affected versions, expressions supplied by authenticated users are evaluated in an execution context that lacks proper isolation from the underlying Node.js runtime (CWE-913). This sandbox escape vulnerability allows arbitrary code to break out of the intended execution boundaries.
2. Exploitation Mechanics & Attack Scenario
An authenticated attacker with permissions to create or edit workflows can exploit this vulnerability by injecting malicious JavaScript payloads into workflow node configuration expressions. When the n8n engine evaluates these expressions—either during manual execution, testing, or automated triggers—the payload executes within the context of the main n8n process. Because the context is not sufficiently sandboxed, the attacker can access Node.js core modules (such as 'child_process') to execute arbitrary shell commands on the host OS or container. This vulnerability is actively exploited in the wild (listed in CISA KEV) by threat actors, including campaigns deploying Zerobot malware to compromise automation servers.
3. Infrastructure & Business Impact
Since n8n is heavily integrated into enterprise environments to automate critical business logic, database operations, and API integrations, a successful compromise has severe consequences. Attackers can extract sensitive credentials, API tokens, and secrets stored within n8n. Furthermore, it provides an initial foothold inside the network, enabling lateral movement, data exfiltration, and deployment of ransomware or botnet agents.
Official Vendor Advisories & References
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.
Frequently Asked SecOps Questions (CVE-2025-68613)
FAQQ1. How critical is CVE-2025-68613 and is it actively exploited in the wild?
CVE-2025-68613 is rated CVSS 8.8 (HIGH) with a 30-day EPSS exploitation probability of 99.0%. It is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, requiring immediate emergency remediation.
Q2. Which vendors and products are affected by CVE-2025-68613?
Primary impacted vendors include n8n across n8n. Scope summary: n8n versions >= 0.211.0 and < 1.120.4, < 1.121.1, < 1.122.0
Q3. What temporary mitigations or workarounds exist for CVE-2025-68613 before patching?
[Mitigation] Immediately upgrade n8n to patched versions (1.120.4, 1.121.1, or 1.122.0 and above) Follow the CLI remediation commands and interactive SecOps checklist on this page to restrict exposure prior to your maintenance window.
Generate an Internal Engineering Notice or CISO Report for CVE-2025-68613
Instantly format this advisory into an executive CISO summary or engineering patch ticket.
🔗 Related Advisories in Similar Stack (n8n)
View Category →GitLab CE/EE Unauthenticated Remote Code Execution (RCE) Advisory (CVE-2026-97229)
[Affected Scope] GitLab CE/EE versions 19.2 (< 19.2.8), 19.3 (< 19.3.5), and 19.4 (< 19.4.2)
GitLab CE/EE Unauthenticated Arbitrary File Read Vulnerability (CVE-2026-85706)
[Affected Scope] GitLab CE/EE versions from 18.7 through 19.3.1.
Google Brotli Decoder Remote Code Execution (RCE) and Memory Corruption Vulnerability (CVE-2026-111497)
[Affected Scope] All web servers, browsers, Node.js environments, and backend applications using Google Brotli library versions 1.0.3 through 1.2.0
JFrog Artifactory Authentication Bypass and Administrative Privilege Escalation (CVE-2026-82329)
[Affected Scope] JFrog Artifactory Self-Managed instances running under default configurations
Subscribe to Daily Vulnerability Briefings & KEV Alerts
Concise morning briefings for SecOps, DevSecOps, and SRE teams covering newly exploited CVEs and mitigation priorities.