CVE-2026-110845 in n8n
Summary
by MITRE • 10/15/2026
n8n before 1.123.83, 2.x before 2.41.4, and 2.42.x before 2.42.1 contains a code execution vulnerability in the Git node Log operation, which fails to strip a repository's local git configuration before invoking an external program. Authenticated members who can point the node, including as an agent tool, at a repository whose local configuration they control can execute programs as the n8n process user.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 10/15/2026
The vulnerability identified in versions of n8n prior to 1.123.83, 2.x before 2.41.4, and 2.42.x before 2.42.1 represents a critical server-side code execution flaw located within the Git node's Log operation. This security defect stems from an improper handling of external inputs during the invocation of system-level commands. Specifically, when the n8n workflow automation platform executes the git log command to retrieve commit history or repository metadata, it fails to sanitize or strip the local git configuration associated with the target repository before passing arguments to the underlying operating system shell. This oversight allows an attacker who has control over the repository's local configuration file to inject malicious commands that are executed by the n8n process user account.
From a technical perspective, this vulnerability is classified under CWE-78 Improper Neutralization of Special Elements used in an OS Command commonly known as OS Command Injection. The root cause lies in the application's failure to validate or escape special characters and configuration directives within the git local config file before it interacts with external programs. In standard Git workflows, the .git/config file can contain various settings that influence how commands are executed. By leveraging specific configurations such as core.hooksPath or other executable hooks, an authenticated user who controls a repository pointed to by the n8n workflow node can manipulate the execution context of the git log command. This manipulation effectively bypasses standard input validation mechanisms because the vulnerability exploits the legitimate behavior of Git itself rather than a direct injection into a raw shell string in many cases, although the result is identical: arbitrary code execution on the host system running the n8n instance.
The operational impact of this vulnerability is severe due to its potential for remote code execution with elevated privileges relative to the application's context. Since authenticated members can configure workflow nodes, including those used as agent tools within automated workflows, they possess a direct vector to trigger this flaw. If an attacker successfully exploits this condition, they gain the ability to execute arbitrary programs on the server hosting n8n. This compromises not only the confidentiality and integrity of the automation platform but also potentially leads to full system compromise if the n8n process runs with sufficient privileges or has access to sensitive internal resources such as databases, API keys, or other microservices within the network architecture. The ability to execute code as the n8n user means that any data accessible by that service account is at risk of exfiltration or modification.
This vulnerability aligns with MITRE ATT&CK technique T1059 Command and Scripting Interpreter, specifically regarding the abuse of system utilities for lateral movement or persistence within an automated environment. It also relates to CWE-284 Improper Access Control because it relies on authenticated access being misused due to insufficient validation of inputs that influence external processes. The risk is particularly acute in environments where n8n is used as a central integration hub, connecting various third-party services and internal systems, thereby increasing the blast radius of any successful exploitation event.
To mitigate this vulnerability, organizations must immediately upgrade their n8n instances to version 1.123.83 or later for the v1 branch, version 2.41.4 or later for the v2.x series prior to 2.42, and version 2.42.1 or later for the 2.42.x line. These updates include patches that properly sanitize repository configurations before invoking external git commands, thereby neutralizing the injection vector. In addition to upgrading, administrators should enforce strict least-privilege principles by ensuring the n8n process runs under a dedicated user account with minimal system permissions and restricted network access. Furthermore, input validation strategies for any workflow nodes interacting with version control systems should be reviewed to ensure that all external inputs are treated as untrusted data until properly validated against allowlists of expected values or safely encoded before processing. Regular security audits of automated workflows can help identify instances where Git nodes point to repositories controlled by less-trusted entities, reducing the attack surface for such injection-based exploits.