Critical n8n Vulnerabilities Allow Authenticated Remote Code Execution (2026)
Executive Summary
In January 2026, cybersecurity researchers uncovered two critical vulnerabilities in the n8n workflow automation platform, including a CVE-2026-1470 flaw (CVSS 9.9) which enables authenticated users to achieve remote code execution via eval injection. Discovered by the JFrog Security Research team, attackers exploiting these weaknesses could bypass the Expression system and execute arbitrary commands on affected servers. Successful exploitation could allow lateral movement and data exfiltration by leveraging internal automation integrations, putting sensitive business processes and connected services at significant risk.
This incident underscores a rising trend of attackers targeting automation and orchestration platforms as high-value footholds in enterprise environments. With the increased adoption of low-code automation, vulnerabilities in such platforms can propagate risk across multiple systems, driving urgent need for software vendors and organizations to prioritize security reviews, patch management, and robust segmentation controls.
Why This Matters Now
The disclosure of these high-severity n8n vulnerabilities highlights the expanding attack surface in automation platforms integral to modern workflows. Their exploitability by authenticated users emphasizes the urgent need for organizations to reassess access controls, update impacted instances, and reevaluate segmentation strategies to prevent privilege escalation and lateral movement before attackers can leverage these flaws in real-world campaigns.
Attack Path Analysis
An attacker with valid n8n credentials exploited the CVE-2026-1470 eval injection vulnerability to achieve remote code execution. After the initial foothold, they escalated privileges to access sensitive workflows or secrets. The attacker attempted to move laterally to adjacent cloud workloads or services by leveraging compromised automation tasks. Command and control was established by creating outbound connections from the n8n host. Sensitive workflow data or secrets were exfiltrated to external endpoints. Ultimately, the attacker could modify or disrupt automation processes, causing operational impact.
Kill Chain Progression
Initial Compromise
Description
The attacker leveraged an eval injection (CVE-2026-1470) using authenticated access to gain code execution on the n8n platform.
Related CVEs
CVE-2026-1470
CVSS 9.9An eval injection vulnerability in n8n's workflow Expression evaluation system allows authenticated users to execute arbitrary code, potentially leading to full system compromise.
Affected Products:
n8n.io n8n – 1.65.0 to 1.120.4
Exploit Status:
proof of conceptCVE-2025-68613
CVSS 8.8A critical Remote Code Execution (RCE) vulnerability in n8n's workflow expression evaluation system allows authenticated users to execute arbitrary code, potentially leading to full system compromise.
Affected Products:
n8n.io n8n – 0.211.0 to 1.120.3
Exploit Status:
proof of concept
MITRE ATT&CK® Techniques
MITRE ATT&CK technique mappings are derived for SEO/filtering; detailed enrichment can be added with STIX/TAXII feeds as needed.
Command and Scripting Interpreter
Exploitation of Remote Services
Valid Accounts
Container Administration Command
Exploitation for Privilege Escalation
Impair Defenses
Phishing
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Address Common Coding Vulnerabilities
Control ID: 6.5.1
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA – ICT Risk Management Framework
Control ID: Article 7(2)
CISA ZTMM 2.0 – Secure Workloads Against Exploitation
Control ID: Workload Pillar - Protection
NIS2 Directive – Implementation of Appropriate Technical and Organisational Measures
Control ID: Article 21(2)
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Information Technology/IT
Critical exposure through n8n workflow automation platform vulnerabilities enabling authenticated remote code execution, compromising automated processes and enterprise integrations.
Financial Services
High-severity eval injection flaws threaten automated financial workflows, payment processing systems, and compliance controls requiring immediate patching and segmentation.
Health Care / Life Sciences
Authenticated RCE vulnerabilities in workflow automation platforms risk patient data exfiltration and HIPAA compliance violations through compromised healthcare processes.
Computer Software/Engineering
Application vulnerability exploitation enables lateral movement through development environments, threatening source code integrity and software supply chain security.
Sources
- Two High-Severity n8n Flaws Allow Authenticated Remote Code Executionhttps://thehackernews.com/2026/01/two-high-severity-n8n-flaws-allow.htmlVerified
- Security Advisory: Security Vulnerability in n8n Versions 1.65-1.120.4https://blog.n8n.io/security-advisory-20260108/Verified
- CVE-2026-1470 Detailhttps://nvd.nist.gov/vuln/detail/CVE-2026-1470Verified
- CVE-2025-68613 Detailhttps://nvd.nist.gov/vuln/detail/CVE-2025-68613Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
This incident highlights critical Zero Trust and CNSF principles: segmentation and strong identity controls can restrict lateral movement and privilege escalation after initial compromise, while workload isolation and egress governance help constrain data exfiltration and command-and-control. Enforcing these controls could have limited attacker actions and visibility throughout the attack chain.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Detection and containment of unauthorized code execution attempts.
Control: Zero Trust Segmentation
Mitigation: Segmentation would restrict access between roles and sensitive resources.
Control: East-West Traffic Security
Mitigation: East-west policies would prevent or flag unauthorized intra-cloud movement.
Control: Multicloud Visibility & Control
Mitigation: Outbound connections would be monitored and policy-enforced to detect command-and-control beacons.
Control: Egress Security & Policy Enforcement
Mitigation: Policy-driven controls limit and log sensitive outbound data flows.
Segmentation, isolation, and governance may have contained the attack and mitigated business impact.
Impact at a Glance
Affected Business Functions
- Workflow Automation
Estimated downtime: 3 days
Estimated loss: $50,000
Potential unauthorized access to sensitive workflow data and system configurations.
Recommended Actions
Key Takeaways & Next Steps
- • Apply microsegmentation and Zero Trust Segmentation to strictly limit workflow and user access across cloud workloads.
- • Enforce egress filtering to control outbound data paths and prevent unauthorized exfiltration by compromised automation platforms.
- • Deploy inline behavioral and anomaly detection for real-time visibility and rapid response to suspicious workflow execution or automation abuse.
- • Utilize east-west traffic controls to restrict lateral movement opportunities following exploitation of workflow automation vulnerabilities.
- • Integrate continuous privileged activity monitoring and policy enforcement for all sensitive cloud automation and orchestration services.
