CVE-2026-1470

Unknown · Unknown Multiple Products

A critical vulnerability has been discovered in the n8n workflow automation platform, identified as CVE-2026-1470.

Executive summary

A critical vulnerability has been discovered in the n8n workflow automation platform, identified as CVE-2026-1470. This flaw allows an authenticated user to execute arbitrary code on the server by crafting malicious expressions within a workflow, potentially leading to a complete system compromise, data theft, and disruption of business operations.

Vulnerability

This is a Remote Code Execution (RCE) vulnerability within the n8n workflow Expression evaluation system. The root cause is insufficient sandboxing of the execution context where user-supplied expressions are processed. An attacker with valid credentials to the n8n instance can create or modify a workflow, embedding a specially crafted expression. When the workflow is executed, this expression is evaluated on the server with the same permissions as the n8n application process, bypassing intended security restrictions and allowing the attacker to run arbitrary system commands.

Business impact

This vulnerability is rated as critical severity with a CVSS score of 9.9. Successful exploitation grants an attacker complete control over the n8n server. The potential business impact is severe and includes the theft of sensitive data processed by workflows (e.g., API keys, customer PII, database credentials), unauthorized modification or deletion of critical business automation, and using the compromised server as a pivot point to attack other internal systems. The reputational damage and financial loss resulting from such a compromise could be substantial.

Remediation

Immediate Action:

  • Patch Immediately: Prioritize updating all affected instances of Unknown Multiple Products to the latest version released by the vendor, which addresses this vulnerability.
  • Monitor and Review: Actively monitor for signs of exploitation, particularly anomalous behavior from the n8n process. Thoroughly review application and system access logs for any suspicious activity, such as unusual workflow modifications or unexpected user logins, preceding the patch.

Proactive Monitoring:

  • Log Analysis: Scrutinize n8n application logs for unusually complex or obfuscated expressions within workflow configurations. Monitor server system logs for unexpected child processes being spawned by the n8n application user (e.g., sh, bash, powershell.exe).
  • Network Traffic: Monitor for anomalous outbound network connections from the n8n server. A sudden connection to an unknown IP address could indicate a reverse shell or data exfiltration.
  • Endpoint Behavior: Utilize an Endpoint Detection and Response (EDR) solution to detect suspicious command execution, file modifications, or other post-exploitation behaviors originating from the n8n process.

Compensating Controls: If patching cannot be performed immediately, implement the following controls to reduce risk:

  • Restrict Access: Enforce the principle of least privilege. Strictly limit and review all user accounts with access to create or modify workflows on the n8n instance.
  • Network Segmentation: Isolate the n8n server from critical internal networks. Implement strict egress filtering to block all outbound network traffic except for what is explicitly required for legitimate workflow operations.
  • Web Application Firewall (WAF): Deploy a WAF with rules designed to detect and block common code injection and command execution payloads within HTTP requests, although this may not be a complete solution.

Exploitation status

Public Exploit Available: False

Analyst recommendation

Given the critical CVSS score of 9.9, this vulnerability represents an immediate and severe threat to the organization. While CVE-2026-1470 is not currently listed on the CISA KEV catalog, its high impact makes it a prime candidate for future inclusion. We strongly recommend that all system owners apply the vendor-supplied patches to affected systems immediately. If patching is delayed, the compensating controls listed above must be implemented as a temporary measure, and a formal plan for patching must be established with the utmost urgency.