Critical n8n Vulnerabilities Expose Automation Nodes to Full Remote Code Execution
Recent discoveries have unveiled critical security flaws within n8n, a widely utilized open-source workflow automation platform. These vulnerabilities, identified as CVE-2026-44789, CVE-2026-44790, and CVE-2026-44791, pose significant risks by potentially allowing attackers to execute arbitrary code on affected systems.
Understanding the Vulnerabilities
The identified vulnerabilities impact several core nodes within n8n, including the HTTP Request, Git, and XML nodes. Each of these flaws carries a critical severity rating, reflecting their potential to compromise system confidentiality, integrity, and availability.
Prototype Pollution in HTTP Request Node (CVE-2026-44789)
The most severe of these issues, CVE-2026-44789, resides in the HTTP Request node. Here, inadequate validation of pagination parameters can lead to prototype pollution—a scenario where attackers manipulate JavaScript object prototypes globally. This manipulation can be exploited to execute arbitrary code on the host system, especially concerning given n8n’s role in integrating with various external APIs and internal systems.
Arbitrary File Read via Git Node (CVE-2026-44790)
CVE-2026-44790 affects the Git node, where attackers can inject malicious command-line interface (CLI) flags during Git push operations. This vulnerability allows unauthorized reading of arbitrary files on the server, potentially exposing sensitive information such as configuration data, credentials, and environment variables. Access to such data can facilitate further exploitation and system compromise.
Patch Bypass in XML Node (CVE-2026-44791)
The third vulnerability, CVE-2026-44791, involves a patch bypass in the XML node. Despite previous fixes, attackers can still exploit prototype pollution through alternative methods. When combined with other vulnerabilities, this flaw can lead to remote code execution, effectively undermining earlier security measures and exposing systems to renewed threats.
Impacted Versions and Remediation
These vulnerabilities affect n8n versions below 1.123.43, 2.20.7, and 2.22.1. The n8n development team has addressed these issues in versions 1.123.43, 2.20.7, 2.22.1, and later. Users are strongly encouraged to upgrade to these patched versions immediately, as no complete workarounds exist.
For organizations unable to implement immediate upgrades, it is advisable to restrict workflow creation and editing permissions to trusted users. Additionally, administrators can disable vulnerable nodes using 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`
However, these measures are temporary and do not fully mitigate the risks associated with these vulnerabilities.
Broader Implications for Automation Platforms
These vulnerabilities underscore the inherent security challenges in automation platforms like n8n. The interconnected nature of nodes and extensible workflows can inadvertently introduce significant security risks. As such, it is imperative for organizations to maintain vigilant security practices, including regular updates, thorough validation of third-party integrations, and stringent access controls.
Conclusion
The discovery of these critical vulnerabilities within n8n serves as a stark reminder of the importance of proactive security measures in the realm of workflow automation. Organizations utilizing n8n should prioritize updating to the latest versions and review their security protocols to safeguard against potential exploits.
