CVE-2026-119408 in n8n
Summary
by MITRE • 10/30/2026
n8n before 2.42.6, 2.43.x before 2.43.3, and 3.x before 3.0.1 contains a remote code execution vulnerability via deprecated Function, Function Item, and LangChain Code nodes running outside task runner isolation. Authenticated users who can create, modify, or import workflows naming these hidden node types can execute JavaScript in the n8n main process.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 10/30/2026
The identified security flaw resides within versions of the n8n automation platform prior to 2.42.6, 2.43.x before 2.43.3, and version 3.x before 3.0.1. This vulnerability constitutes a critical remote code execution risk that stems from the improper handling of specific node types within workflow definitions. The affected components include deprecated Function nodes, Function Item nodes, and LangChain Code nodes. These elements are designed to allow users to inject custom JavaScript logic into their automation workflows. However, in the vulnerable versions, these nodes were executed outside of a secure task runner isolation environment when accessed through certain code paths or configuration states. This architectural oversight means that the JavaScript code injected by an authenticated user is not sandboxed but instead runs directly within the main process of the n8n application server.
The operational impact of this vulnerability is severe, as it allows any authenticated user with permissions to create, modify, or import workflows containing these specific node types to achieve arbitrary command execution on the host system running n8n. Since the code executes in the context of the primary application process, an attacker can potentially access sensitive environment variables, read configuration files, interact with internal APIs, or pivot further into other systems connected to the network where n8n is deployed. This effectively bypasses standard authentication controls because the execution privilege escalates from a user-level operation to that of the service account running the n8n process. The risk is particularly acute in multi-tenant environments or shared instances where users may not fully trust each other, as one malicious actor can compromise the entire infrastructure by exploiting this code injection vector through workflow manipulation rather than direct network exploitation against the web server itself.
From a classification perspective, this vulnerability aligns with CWE-94 Improper Control of Generation of Code (Code Injection) and specifically relates to CWE-78 OS Command Injection if the executed JavaScript leads to shell commands being run via child processes or similar mechanisms. In terms of adversary behavior mapping under MITRE ATT&CK, this scenario corresponds to T1059 Command and Scripting Interpreter, where an attacker uses a scripting language like JavaScript to execute malicious code on a target system. It also touches upon T1190 Exploit Public-Facing Application if the workflow import or modification is triggered via exposed endpoints, although the primary vector here relies on authenticated access rather than unauthenticated exploitation. The lack of isolation for these specific node types represents a failure in defense-in-depth principles, where expected sandboxing mechanisms were either absent or bypassed due to legacy code paths that did not enforce strict execution boundaries.
To mitigate this risk, organizations running affected versions must immediately upgrade n8n to version 2.43.3 or later for the 2.x branch and version 3.0.1 or later for the 3.x branch. These updates address the isolation issues by ensuring that all code nodes, including deprecated ones, are executed within a secure task runner environment that restricts access to system resources and prevents direct manipulation of the main process memory space. Until an upgrade is performed, administrators should enforce strict role-based access control policies to limit which users can create or modify workflows containing Function or LangChain Code nodes. Additionally, auditing workflow imports for suspicious JavaScript payloads and disabling unused deprecated node types where possible can reduce the attack surface. Monitoring logs for unusual execution patterns related to these specific node types may also help in detecting attempted exploitation activities before they result in full system compromise.