Loading story…
Security researchers reported critical vulnerabilities in the open-source workflow automation platform n8n that can enable server takeover and credential compromise, with particular risk to AI-orchestration use cases where workflows handle sensitive API keys and prompts. Pillar Security described a pair of maximum-severity sandbox escape issues (patched in n8n 2.4.0) that could allow attackers to intercept prompts, tamper with AI outputs, divert traffic, and exfiltrate sensitive data; they also warned that a single compromised n8n Cloud account could be leveraged to access shared Kubernetes infrastructure and potentially other customers’ data. Recommended mitigations included immediate patching, rotating encryption keys and credentials, and auditing/monitoring workflows for abuse.
Separately, Cyble reported observed attack attempts against CVE-2025-68613, described as a critical RCE condition in n8n where authenticated users can supply workflow expressions that execute in an insufficiently isolated context, potentially leading to arbitrary code execution with n8n privileges and full system compromise. Cyble stated the issue is fixed in n8n 1.120.4, 1.121.1, and 1.122.0, and noted broader attacker interest in newly disclosed vulnerabilities with public PoCs—raising the likelihood of near-term exploitation for exposed or unpatched n8n deployments.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
Researchers reported that n8n was affected by two maximum-severity sandbox escape vulnerabilities that could be chained for full server takeover, credential compromise, prompt interception, and data exfiltration. The issues were patched in n8n version 2.4.0, with users advised to upgrade and rotate keys and credentials.
Cyble reported that its honeypots detected attack attempts exploiting CVE-2025-68613, indicating active interest in the critical n8n flaw. The report also highlighted broader threat-actor discussion and exploitation activity around other high-impact vulnerabilities.
A critical remote code execution vulnerability tracked as CVE-2025-68613 in the n8n workflow automation platform was fixed in versions 1.120.4, 1.121.1, and 1.122.0. The flaw increased the risk of real-world exploitation against exposed n8n deployments.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Researchers reported **critical vulnerabilities in the n8n low-code workflow automation platform** that can enable **host-level compromise**. The issues include **CVE-2026-1470 (CVSS 9.9)** and **CVE-2026-0863 (CVSS 8.5)**, described as allowing attackers to **bypass security controls**, achieve **arbitrary code execution**, and potentially obtain **full control of n8n services**, with downstream exposure of **credentials, API keys, and other sensitive data**. Impact spans **cloud deployments** as well as **self-hosted instances** that have not been patched. Given n8n’s common use to integrate SaaS services and increasingly to orchestrate **LLM-enabled business workflows**, successful exploitation could provide broad access to connected systems and secrets stored in workflows. Coverage also noted the disclosures follow an earlier, separate critical n8n issue reported in late 2025, reinforcing the need for tighter vulnerability management around automation/orchestration tooling. Organizations were urged to **upgrade to patched versions** and review hardening controls for n8n deployments, particularly where the platform has access to high-privilege tokens and production integrations.
Jun 29, 2026
A **critical remote code execution** issue in the *n8n* open-source workflow automation platform, tracked as **CVE-2026-25049** (also published as **GHSA-6cqr-8cfr-67f8**), allows an **authenticated** user with permission to create or modify workflows to escape n8n’s expression sandbox and execute arbitrary system commands on the underlying host. The flaw stems from **insufficient input sanitization/weak sandboxing** in n8n’s expression evaluation (server-side JavaScript) and was identified during follow-up analysis after an earlier critical n8n vulnerability (**CVE-2025-68613**) was patched; researchers report the new issue effectively **bypasses prior mitigations**. Reporting indicates exploitation can lead to **full compromise** of the n8n instance, including access to the filesystem and the ability to **steal stored credentials and secrets** (e.g., API keys, OAuth tokens) and sensitive configuration, with potential for **pivoting** into connected internal services and cloud accounts in multi-tenant deployments. Public reporting also notes **public exploits** are available. n8n maintainers state the issue is patched, and affected organizations should upgrade to fixed releases (**1.123.17** and **2.5.2**), as versions **prior to 1.123.17 and 2.5.2** are impacted.
Jun 29, 2026
A critical vulnerability, CVE-2025-68613, has been discovered in the n8n open-source workflow automation platform, allowing authenticated users with workflow creation or editing permissions to execute arbitrary system commands on the underlying server. This flaw, rated 9.9 on the CVSS scale, stems from improper sandboxing of JavaScript expressions within workflow definitions, enabling attackers to escape restrictions and gain system-level access. The vulnerability does not require administrative privileges, making it a significant risk in environments with multiple users or weak access controls, and could lead to full system compromise, data exfiltration, workflow sabotage, and lateral movement. Another related vulnerability, CVE-2025-68668, also enables sandbox escape in n8n, turning workflows into potential attack vectors. Both vulnerabilities highlight the urgent need for organizations using n8n to review user permissions, apply available patches, and implement strong access controls to mitigate the risk of exploitation. While there is no current evidence of active exploitation, the ease of attack and the platform's popularity make immediate remediation essential.
Jun 29, 2026