Critical n8n RCE Vulnerabilities Expose Automation Workflows

Key Takeaways

• Critical vulnerabilities have been discovered in the n8n workflow automation platform, potentially leading to full remote code execution.
• Three distinct flaws (CVE-2026-44789, CVE-2026-44790, CVE-2026-44791) impact core n8n components, including HTTP Request, Git, and XML nodes.
• Exploitation requires only low-privileged authenticated access with workflow editing permissions.
• Patches are available in n8n versions 1.123.43, 2.20.7, and 2.22.1 and later; immediate upgrades are strongly recommended.

Significant security concerns have emerged following the discovery of critical vulnerabilities within the widely used workflow automation platform, n8n. Cybersecurity researchers have issued warnings that these flaws, if exploited in sequence, could grant attackers complete remote code execution (RCE) capabilities on affected systems.

The vulnerabilities, detailed in GitHub Security Advisories, are identified as CVE-2026-44789, CVE-2026-44790, and CVE-2026-44791. They affect several fundamental n8n components, specifically the HTTP Request, Git, and XML nodes. Each of these issues is rated as critical, with their CVSS scores indicating a substantial impact across confidentiality, integrity, and availability metrics.

Security researcher Jubke published the advisories on GitHub, underscoring how authenticated users with minimal privileges—specifically those with workflow editing permissions—could leverage these weaknesses to compromise entire n8n instances.

n8n Vulnerabilities

Prototype Pollution Leads to RCE

The most severe of the identified issues, CVE-2026-44789, resides within the HTTP Request node. This flaw stems from inadequate validation of pagination parameters, which allows an attacker to trigger prototype pollution. Categorized under CWE-1321, this vulnerability permits the manipulation of JavaScript object prototypes at a global level.

In practice, this means an attacker can inject malicious properties into application objects. These injected properties can then be leveraged, often in conjunction with other exploitation techniques, to execute arbitrary code on the underlying host system. Given that n8n workflows frequently interact with both external APIs and internal infrastructure, this vulnerability considerably expands the potential attack surface, particularly in environments heavily reliant on automation.

Git Node Enables Arbitrary File Read

A second critical vulnerability, CVE-2026-44790, impacts the Git node. This flaw could allow malicious actors to inject arbitrary command-line interface (CLI) flags during Git push operations. This argument injection, classified under CWE-88, enables attackers to read sensitive files from the server, including configuration data, credentials, and environment variables. Such access frequently serves as a direct pathway to full system compromise.

XML Node Patch Bypass Reopens Risk

The third vulnerability, CVE-2026-44791, represents a patch bypass in the XML node. Despite previous attempts to fix a related issue, attackers can still exploit prototype pollution through alternative execution paths. When combined with other vulnerable nodes, this flaw can also lead to remote code execution, effectively nullifying prior security measures and re-exposing systems that were presumed to be protected.

Affected Versions and Fixes

All three vulnerabilities impact n8n versions prior to 1.123.43, 2.20.7, and 2.22.1. Patches have been released in versions 1.123.43, 2.20.7, 2.22.1, and all subsequent releases. Users are strongly urged to upgrade their n8n instances immediately, as no complete workaround currently exists.

For organizations unable to apply patches immediately, researchers recommend restricting workflow creation and editing permissions exclusively to trusted personnel. Administrators can also disable the vulnerable nodes by utilizing the NODES_EXCLUDE environment variable:

• To disable the HTTP Request node: n8n-nodes-base.httpRequest
• To disable the Git node: n8n-nodes-base.git
• To disable the XML node: n8n-nodes-base.xml

It is important to note that these mitigation steps are temporary and do not fully eliminate the inherent risk. These disclosures underscore a broader cybersecurity challenge present in automation platforms like n8n, where interconnected nodes and extensible workflows can inadvertently amplify the severity of individual flaws. Given that low-privileged access is sufficient for exploitation, organizations relying on n8n for critical automation must prioritize this disclosure and ensure prompt remediation. Failure to do so could enable attackers to escalate from basic workflow access to complete system control in a matter of minutes.

What You Should Do

• Upgrade Immediately: Apply the latest n8n patches to versions 1.123.43, 2.20.7, 2.22.1, or newer. This is the most effective and recommended mitigation.
• Restrict Permissions: If immediate patching is not feasible, strictly limit workflow creation and editing permissions to only trusted, high-privileged users.
• Disable Vulnerable Nodes: As a temporary measure, use the NODES_EXCLUDE environment variable to disable the HTTP Request, Git, and XML nodes if their functionality is not critical to your operations.
• Review Access Controls: Regularly audit and enforce strict access controls for all users with workflow editing capabilities within your n8n environment.

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.