CVE-2026-56352 in n8n
Summary
by MITRE • 07/15/2026
n8n before 2.19.3 contains a file path restriction bypass in the legacy ExecuteWorkflow node's localFile source option, which reads workflow files from disk without the file-access checks enforced by other file-reading nodes. Although hidden from the UI since v1.2, it remains reachable via the REST API. An authenticated user with permission to create or modify workflows can supply an arbitrary file path to bypass the N8N_RESTRICT_FILE_ACCESS_TO restriction and determine whether arbitrary files exist on the host; where the targeted path contains a valid workflow JSON file, that file can additionally be loaded and executed.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 07/15/2026
The vulnerability in n8n versions prior to 2.19.3 represents a critical security flaw that undermines the platform's file access controls through a legacy component that remains accessible via API despite being hidden from the user interface. This issue stems from the ExecuteWorkflow node's localFile source option, which operates outside the normal file access validation mechanisms that protect other file-reading components within the application. The flaw exists because the legacy node bypasses the N8N_RESTRICT_FILE_ACCESS_TO restriction that should normally prevent unauthorized file system access, creating a pathway for malicious exploitation.
The technical implementation of this vulnerability allows an authenticated user with workflow creation or modification privileges to manipulate the localFile parameter through the REST API interface. This bypass occurs because the legacy ExecuteWorkflow node does not enforce the same security checks that are applied to other file-reading operations within the platform. The restriction mechanism that should limit file access to predefined safe paths is completely circumvented when using this specific node variant, enabling attackers to traverse the file system and access files that would normally be protected. This represents a classic path traversal vulnerability where the application fails to properly validate or sanitize user-supplied file paths before attempting to read them from the host filesystem.
The operational impact of this vulnerability extends beyond simple file enumeration to include potential code execution capabilities when valid workflow JSON files are targeted. An attacker can not only determine the existence of arbitrary files on the host system but can also load and execute workflow definitions that contain malicious payloads. This creates a significant risk for organizations using n8n in production environments where workflow files might contain sensitive data or where attackers could leverage this vulnerability to escalate privileges within the system. The bypass affects both the detection and execution phases of an attack, as it allows for reconnaissance followed by direct exploitation of workflow processing capabilities.
Security mitigations for this vulnerability require immediate patching to n8n version 2.19.3 or later where the restriction bypass has been addressed through enhanced input validation and consistent enforcement of file access controls across all nodes. Organizations should also implement additional monitoring around REST API endpoints that handle workflow execution, particularly focusing on unusual patterns in file path parameters that might indicate exploitation attempts. The vulnerability aligns with CWE-22 Path Traversal and CWE-73 Path Traversal in the Common Weakness Enumeration catalog, while also mapping to ATT&CK technique T1059 Command and Scripting Interpreter where attackers could leverage this vulnerability to execute arbitrary workflow code. System administrators should review and tighten access controls for workflow modification permissions, as the attack surface is expanded by users who possess sufficient privileges to manipulate workflow definitions through the API interface.