A critical vulnerability in n8n’s workflow automation platform allows authenticated attackers to break out of security sandboxes and execute arbitrary code on the underlying server. CVE-2025-68613, scored CVSS 9.9 affects n8n versions from 0.211.0 through 1.120.4 and has been actively exploited according to CISA’s Known Exploited Vulnerabilities catalogue. More than 24,700 unpatched instances remain exposed online as of early March 2026.
The vulnerability sits in n8n’s expression evaluation engine which processes JavaScript code within workflow definitions without sufficient isolation. Authenticated users, even those with minimal privileges, can inject malicious expressions that escape the intended sandbox and execute with the same privileges as the n8n process. Orca Security describes it as enabling “arbitrary code on the underlying server via expression injection” with full server compromise potential.
Attackers Need Just Basic Authentication
Unlike many workflow automation attacks that require administrative access, CVE-2025-68613 can be exploited by any authenticated user with workflow creation or editing permissions. The attack works by submitting specially crafted JavaScript expressions within workflow nodes. When n8n evaluates these expressions during workflow execution, the malicious code escapes the sandbox and gains full access to the Node.js runtime and underlying operating system.
Resecurity’s analysis shows the vulnerability “directly undermines all three pillars of the Confidentiality, Integrity and Availability (CIA) triad.” Successful exploitation grants attackers unrestricted access to API keys, OAuth tokens, database credentials and service secrets stored within n8n workflows. Because n8n typically serves as central orchestration connecting internal systems and cloud services, compromise often cascades across entire organizations.
100,000 Vulnerable Instances Were Exposed at Disclosure
SOCRadar estimates more than 100,000 internet-reachable n8n instances were vulnerable when CVE-2025-68613 was disclosed in December 2025. Significant concentrations were identified in the United States, Germany, France, Brazil and Singapore. Current Shadowserver Foundation data shows more than 24,700 instances remain unpatched with 12,300 in North America and 7,800 in Europe.
The scale matters because n8n is increasingly deployed in DevOps, customer support and fintech environments where it handles sensitive credentials and automates business-critical processes. Threat Landscape notes that organizations “relying on automation for DevOps, Customer Support and FinTech are at high risk due to the sensitive nature of the API keys” typically stored in n8n credentials.
Public proof-of-concept exploits are available and CISA’s addition to the KEV catalogue in March 2026 confirms active exploitation in the wild. The agency has ordered Federal Civilian Executive Branch agencies to patch their n8n instances by 25 March 2026.
Multiple Related Flaws Create Attack Chains
CVE-2025-68613 is part of a cluster of critical n8n vulnerabilities disclosed over recent weeks. Rapid7 identified four additional CVEs that can be chained together for more sophisticated attacks, CVE-2026-21858 (CVSS 10.0) enables unauthenticated file access while CVE-2026-21877 (CVSS 9.9) allows remote code execution via arbitrary file write. Security researcher Valentin Lobstein published a proof-of-concept that chains CVE-2026-21858 with CVE-2025-68613 to achieve unauthenticated remote code execution.
Threat Landscape reports that CVE-2026-25049, a bypass for the original CVE-2025-68613 fix was disclosed in February 2026. This pattern of multiple bypasses suggests the underlying architectural issues in n8n’s expression evaluation system are more fundamental than initially assessed.
Patch Now, Audit Later
Immediate patching is required. n8n versions 1.120.4, 1.121.1 and 1.122.0 contain fixes for CVE-2025-68613. For the more recent bypass CVE-2026-25049, upgrade to version 1.123.17 or 2.5.2 or higher. These patches introduce proper sandboxing controls that prevent expressions from escaping their intended execution context.
If immediate patching is not possible, restrict workflow creation and editing to a minimal trusted user group, implement network segmentation to isolate n8n instances and audit webhook configurations to ensure public-facing webhooks use proper authentication rather than “None.” Review all stored credentials and API keys for signs of unauthorized access.
The Canadian Centre for Cyber Security and multiple security firms have published indicators of compromise scanners for environments that may have been breached before patching. Given the six-week window between initial exploitation and CISA’s KEV listing, assume any unpatched internet-facing n8n instance was potentially compromised.
References
- CVE-2025-68613 Critical n8n RCE & Server Compromise
- Ni8mare and N8scape Flaws Among Multiple Critical Vulnerabilities Affecting n8n
- CVE-2025-68613 Critical RCE Vulnerability Disclosed in n8n
- CISA Flags Actively Exploited n8n RCE Bug as 24,700 Instances Remain Exposed
- Canadian Centre for Cyber Security: AL26-001 Vulnerabilities Affecting n8n
- n8n GitHub Security Advisory: CVE-2025-68613
- CISA Known Exploited Vulnerabilities Catalogue
This post is also available in:
May 20, 2026