A severe security flaw has been uncovered in the popular open-source workflow automation platform n8n, exposing more than 103,000 potentially vulnerable instances worldwide to the risk of arbitrary code execution. Tracked as CVE-2025-68613 and rated 9.9 (Critical) on the Common Vulnerability Scoring System (CVSS), the vulnerability’s exploitation could result in full takeover of affected environments if not promptly mitigated
High-Severity RCE Threat Emerges in Workflow Automation
Security researchers and project maintainers indicate the flaw lies within n8n’s workflow expression evaluation system, where user input expressions are insufficiently sandboxed from the underlying runtime environment. This design weakness means that authenticated users, even those with modest privileges like workflow editing rights, could submit crafted expressions capable of executing operating-system level commands with the same privileges as the n8n process itself. Successful exploitation would allow attackers to access sensitive data, modify workflows, and execute system functions outside of intended automation logic.
According to advisories, the bug affects n8n versions from 0.211.0 up to but excluding the patched releases — 1.120.4, 1.121.1, and 1.122.0. Users running older release branches should consider upgrading immediately to one of these fixed versions to eliminate exposure.
Global Scope and Attack Surface
Analysis by attack surface mapping firm Censys highlights over 103,476 potentially exposed n8n instances as of December 22, 2025, predominantly located in the United States, Germany, France, Brazil, and Singapore. These deployments span self-hosted instances, enterprise environments, and various cloud settings.
The widespread adoption of n8n — which averages approximately 57,000 weekly downloads from npm — further emphasizes the scale of possible impact for organizations relying on automated workflows in both development and production contexts.
Why This Matters: Risks Beyond Workflow Failures
The critical nature of this vulnerability stems from more than just arbitrary code execution. In many deployments, workflows orchestrate tasks such as API calls, data transformations, and service integrations — all with access to sensitive credentials or internal systems. An attacker capable of issuing system-level commands could:
- Exfiltrate confidential data or environment variables containing API keys and credentials
- Modify or disable existing workflows in unpredictable ways
- Leverage the compromised host as a springboard for internal lateral movement
- Disrupt operational automation and business processes at scale
While exploitation currently requires authentication, this does not reduce urgency for remediation. Many production environments have broad internal access, shared credentials, or weak segmentation, increasing the likelihood that attackers could leverage existing credentials or compromised accounts to trigger the flaw.
Expert Insights and Mitigation Strategies
Security practitioners advise that beyond simply applying patches, organizations should harden deployment environments and review permission models. Restricting workflow creation and editing to a trusted set of users — and minimizing administrative privileges — can significantly reduce exploitation risk in the short term. Additionally, isolating the n8n process with limited operating-system privileges and enforcing network access controls adds further defensive layers against misuse of this vulnerability.
A spokesperson for a vulnerability research group noted, “This class of flaw highlights the dangers of insufficient sandboxing in low-code/no-code workflow platforms. As automation proliferates deeply into business processes, defenders must balance ease of use with strict execution boundaries.” (Expert insight synthesized from industry best practices)
Conclusion
The disclosure of CVE-2025-68613 represents a stark reminder of the security risks embedded in increasingly popular workflow automation tools. With a near-maximum CVSS severity rating and a global footprint of vulnerable instances, it serves as an urgent call to action for developers, IT leaders, and security teams alike.
Applying the available patches — n8n 1.120.4, 1.121.1, or 1.122.0 — is the first step. Organizations unable to update immediately must implement temporary mitigations such as strict access controls and hardened runtime environments to avoid realizing worst-case outcomes. The significance of this vulnerability lies not only in its critical rating but in its potential to impact entire automation ecosystems if left unaddressed.
Please subscribe to the Newsletter so that you do not miss any critical update