n8n before 2.19.3 contains a path traversal flaw in the legacy ExecuteWorkflow node’s localFile source option. The node bypasses the N8N_RESTRICT_FILE_ACCESS_TO restriction and reads workflow files from disk without the file‑access checks enforced by other nodes. An authenticated user with permission to create or modify workflows can supply an arbitrary file path, determine whether the file exists on the host, read its contents, and if the file contains a valid workflow JSON it will be loaded and executed. This results in both arbitrary file read and the potential for malicious workflow execution.

Versions of the n8n workflow automation platform prior to 2.19.3 are affected. The weakness resides in the core n8n product, specifically the legacy ExecuteWorkflow node that is hidden from the UI since v1.2 but still reachable via the REST API.

The CVSS score of 5.3 indicates moderate severity, and the EPSS score of less than 1 % suggests that exploitation is currently unlikely. The vulnerability is not listed in CISA KEV. However, exploitation is possible through the REST API by any authenticated user who can create or modify workflows. The attacker can supply an arbitrary file path, read sensitive host files, and if a workflow JSON file is present, load and execute it, giving the attacker control over the workflow engine. The potential impact includes data disclosure and code execution within the n8n instance.