CVE-2026-44790 Overview
CVE-2026-44790 is a critical argument injection vulnerability [CWE-88] affecting n8n, an open source workflow automation platform. The flaw exists in the Git node's Push operation, where an authenticated user with permission to create or modify workflows can inject command-line interface (CLI) flags into the underlying Git invocation. Successful exploitation enables an attacker to read arbitrary files from the n8n server, which can lead to full host compromise. The vulnerability impacts versions prior to 1.123.43, 2.22.1, and 2.20.7.
Critical Impact
Authenticated workflow editors can inject Git CLI flags to read arbitrary files from the n8n server and escalate to full system compromise.
Affected Products
- n8n versions prior to 1.123.43
- n8n versions prior to 2.22.1
- n8n versions prior to 2.20.7
Discovery Timeline
- 2026-06-23 - CVE-2026-44790 published to the National Vulnerability Database (NVD)
- 2026-06-24 - Last updated in NVD database
Technical Details for CVE-2026-44790
Vulnerability Analysis
The vulnerability stems from improper neutralization of argument delimiters [CWE-88] in the Git node's Push operation. The node constructs a git push command using user-controllable workflow parameters and passes them to the Git binary without sufficient validation. An authenticated user with workflow create or modify privileges can craft input that the Git CLI interprets as additional flags rather than as positional arguments. Because Git supports flags that influence file references, output destinations, and hook execution, the injected flags can be abused to read or write arbitrary files accessible to the n8n process. The attack requires only low privileges and no user interaction, executed over the network through the n8n editor or API.
Root Cause
The root cause is the absence of an argument terminator (such as --) and the lack of strict input validation when assembling the Git command line in the Push operation handler. User-supplied strings that begin with - or -- are forwarded to Git as options, allowing attacker-controlled flags to alter the binary's behavior.
Attack Vector
An authenticated attacker with workflow editing rights creates or modifies a workflow that uses the Git node configured for a Push operation. By supplying a remote, branch, or path parameter that contains crafted CLI flags, the attacker manipulates Git's behavior to disclose file contents from the n8n server filesystem. Refer to the n8n GitHub Security Advisory GHSA-57g9-58c2-xjg3 for additional technical context.
Detection Methods for CVE-2026-44790
Indicators of Compromise
- Workflow definitions containing Git node Push parameters with values beginning with - or --, or containing --upload-pack, --receive-pack, or --exec style options.
- Unexpected reads of sensitive files such as /etc/passwd, SSH private keys, or n8n credential stores by the n8n process user.
- Outbound Git operations to unfamiliar remotes initiated by authenticated low-privilege users.
Detection Strategies
- Audit existing workflows for Git node Push configurations and inspect parameter values for shell metacharacters or leading dash characters.
- Monitor n8n audit logs for workflow create and update events authored by non-administrative accounts that reference the Git node.
- Inspect process telemetry for git child processes spawned by the n8n runtime that include unusual flags or reference filesystem paths outside the repository working directory.
Monitoring Recommendations
- Forward n8n application logs and host process events to a centralized analytics platform and alert on git invocations originating from the n8n service account that include flags outside an allowlist.
- Track file access on the n8n host for sensitive paths and correlate with workflow execution identifiers.
- Establish a baseline of expected Git remotes and alert on deviations.
How to Mitigate CVE-2026-44790
Immediate Actions Required
- Upgrade n8n to version 1.123.43, 2.22.1, or 2.20.7 or later, depending on the deployed release line.
- Review the list of users with workflow create or modify permissions and remove unnecessary access.
- Audit all existing workflows that include the Git node and remove or sanitize any suspicious Push parameters.
Patch Information
The vulnerability is fixed in n8n 1.123.43, 2.22.1, and 2.20.7. See the n8n GitHub Security Advisory GHSA-57g9-58c2-xjg3 for official remediation guidance.
Workarounds
- Restrict workflow creation and modification permissions to a small set of trusted administrators until patching is complete.
- Run the n8n service under a dedicated low-privilege account with filesystem access limited to required directories.
- Disable or block the Git node in environments where Git integration is not required.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
