CVE-2026-77068 in n8n
Summary
by MITRE • 08/20/2026
n8n before 2.33.4 and 2.34.x before 2.34.1 contain a remote code execution vulnerability in the @n8n/workflow-sdk node-schema loader used for MCP node-schema loading. The loader derives a node's schema module path directly from the attacker-supplied node type string without validating path-traversal sequences. An authenticated user with global:member privileges can reference malicious files via path traversal, causing code execution in the n8n main process.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 08/20/2026
The vulnerability identified affects versions of n8n prior to 2.33.4 and version 2.34.x prior to 2.34.1, specifically within the @n8n/workflow-sdk component responsible for loading node schemas via the Model Context Protocol interface. This flaw constitutes a critical remote code execution vulnerability stemming from improper validation of user-supplied input during the dynamic module resolution process. The core technical issue lies in how the loader constructs the file path for importing schema definitions. Instead of sanitizing or strictly validating the node type string provided by the client, the system directly concatenates this input into the filesystem path used to locate and load the corresponding JavaScript module. This lack of rigorous boundary checking allows an attacker to inject directory traversal sequences, such as dot-dot-slash characters, into the node type parameter.
By exploiting this path traversal mechanism, an authenticated user possessing global:member privileges can manipulate the file system access controls inherent in the Node.js runtime environment used by n8n. The attacker can craft a request that causes the loader to resolve paths outside of the intended application directory structure. This enables the reference and subsequent loading of arbitrary files from the server's filesystem, including potentially sensitive configuration files or malicious scripts placed within accessible directories. When the main process attempts to execute these loaded modules as part of its normal workflow initialization routine, it inadvertently executes code defined by the attacker. This results in full remote code execution with the privileges of the n8n service account, which often runs with significant system access depending on deployment configurations.
The operational impact of this vulnerability is severe due to the high level of authentication required and the potency of the resulting exploit. While an attacker must first authenticate as a global member, this privilege level is relatively common in many organizational deployments where users are granted broad permissions to create workflows or manage integrations. Once authenticated, the ability to execute arbitrary code on the host system allows for complete compromise of the n8n instance and potentially lateral movement within the internal network if the service account has excessive privileges. The attacker could exfiltrate sensitive data processed by automation workflows, modify existing automations to perform unauthorized actions, or use the compromised server as a pivot point for further attacks against other infrastructure components. This aligns with CWE-22, which describes Improper Limitation of a Pathname to a Restricted Directory, and maps to MITRE ATT&CK techniques related to Command and Scripting Interpreter execution via file system manipulation.
Mitigation strategies must prioritize immediate version upgrades as the primary defense vector. Organizations running affected versions should upgrade n8n to version 2.34.1 or later, where this path traversal logic has been corrected with proper input validation and safe path resolution methods that prevent directory escape sequences from being processed. In environments where upgrading is not immediately feasible, network-level controls such as web application firewalls can be configured to detect and block HTTP requests containing suspicious path traversal patterns in parameters associated with node schema loading. Additionally, enforcing the principle of least privilege for service accounts running n8n reduces the blast radius should an exploitation occur by limiting the file system access rights available to the main process. Regular auditing of user permissions ensures that only necessary personnel hold global:member status, thereby reducing the attack surface available to potential adversaries seeking to leverage this vulnerability for unauthorized code execution.