CVE-2026-44790: n8n Git Node Command Injection – Patching Guidance

Technical summary

The vulnerability exists in n8n's Git node Push operation, which fails to properly sanitize user-supplied input before constructing CLI commands. An authenticated attacker with workflow creation or modification permissions can inject arbitrary Git command-line flags through the Push operation interface. This command injection (CWE-88) allows execution of shell commands in the context of the n8n server process, enabling file disclosure and potentially code execution. The attack requires authentication and workflow manipulation privileges but otherwise faces no execution barriers (network-accessible, no complex interaction required). Versions prior to 1.123.43 (v1.x branch), 2.20.7 (v2.x branch), and 2.22.1 (v2.x branch) are vulnerable.

Business impact

This vulnerability poses significant risk to organizations relying on n8n for workflow automation. An insider or compromised workflow designer can exfiltrate configuration files, credentials, API keys, and sensitive data handled by workflows. In multi-tenant deployments, attackers may access data belonging to other tenants. The high CVSS score (8.8) reflects the combination of broad impact—confidentiality, integrity, and availability—with relatively low barriers to exploitation by insiders. Organizations should prioritize patching to prevent both accidental misuse and intentional data breaches.

Affected systems

n8n workflow automation platform across all deployment models (self-hosted, cloud, containerized). Specifically affected versions include the entire 1.x branch prior to 1.123.43, version 2.20.x prior to 2.20.7, and version 2.21.x and 2.22.0. Users on 2.22.1 or later, 2.20.7 or later, and 1.123.43 or later are not affected. The vulnerability requires the attacker to have authenticated access with workflow creation or modification permissions.

Exploitability

Exploitability is moderate-to-high for insider threats and high-privilege threat actors. An authenticated user with workflow design permissions can inject CLI flags into any Git Push operation without special tooling or complex setup. No user interaction is needed once the malicious workflow is created. However, the attack is limited to authenticated users—external attackers must first compromise valid credentials or be granted workflow access. The lack of current inclusion in the CISA Known Exploited Vulnerabilities (KEV) catalog does not indicate low exploitability; it reflects the vulnerability's recent publication date and potential limited disclosure.

Remediation

Update n8n to version 1.123.43 or later (for v1.x users), 2.20.7 or later (for v2.x users on the stable branch), or 2.22.1 or later (for v2.x users on newer versions). Organizations should verify their running version, plan upgrade windows for business continuity, and test patches in non-production environments before deployment. After patching, audit workflow history and Git push activities for signs of exploit attempts.

Patch guidance

Consult the n8n release notes and official security advisories for detailed patch instructions specific to your deployment model (Docker, npm, self-hosted). For self-hosted installations, backup configuration and workflow definitions before upgrading. For managed n8n cloud environments, coordinate with n8n to confirm patch application. Verify the patched version is running by checking the web UI version display or API endpoint. Given the authentication requirement, prioritize patching systems accessible to workflow designers.

Detection guidance

Monitor Git node configurations and workflow edits for suspicious CLI flags or unusual git command patterns. Audit authentication logs for unusual workflow creation or modification activity, especially by accounts not typically involved in automation design. Check for exfiltration patterns in file access logs or network logs from the n8n server process. Review workflow execution logs for failed or unexpected git operations. If running n8n with detailed logging, search for git command construction events that contain unusual flags like --exec or shell metacharacters.

Why prioritize this

This vulnerability merits immediate attention due to its high CVSS score (8.8), broad impact on confidentiality and integrity, and low barriers to exploitation by insiders. The requirement for authentication somewhat limits blast radius, but workflow automation platforms often have multiple authorized designers. The potential for full server compromise, including credential and data theft, elevates priority for any organization using n8n in production.

Risk score, explained

The CVSS 3.1 score of 8.8 (HIGH) reflects: (1) network-accessible attack vector; (2) low attack complexity (straightforward flag injection); (3) low privilege bar (authenticated user with workflow permissions, a common role); (4) no user interaction required; (5) full impact on confidentiality, integrity, and availability (code/command execution). The score does not account for the requirement for valid credentials; organizations with strong access controls may experience lower practical risk, but should not rely on this as primary mitigation.

Frequently asked questions