Recent discoveries of critical vulnerabilities in the widely used workflow automation platform, n8n, have heightened security concerns. Experts caution that multiple flaws can be combined, leading to potential remote code execution (RCE) on affected systems.
Key Vulnerabilities and Their Impact
The vulnerabilities, identified through GitHub Security Advisories and denoted as CVE-2026-44789, CVE-2026-44790, and CVE-2026-44791, affect core nodes in n8n such as HTTP Request, Git, and XML nodes. These issues are marked with critical severity, underscoring their potential impact on confidentiality, integrity, and availability.
Security expert Jubke outlined these advisories on GitHub, emphasizing that even low-privileged users with workflow editing rights could exploit these flaws, compromising entire n8n systems.
Prototype Pollution and Its Consequences
The most severe flaw, CVE-2026-44789, is located in the HTTP Request node. It involves inadequate validation of pagination parameters, resulting in prototype pollution. This vulnerability, categorized under CWE-1321, allows for global manipulation of JavaScript object prototypes.
This means attackers can inject harmful properties into application objects, which can be used with other techniques to run arbitrary code. Since n8n workflows often connect with external APIs and internal systems, this flaw broadens the attack vector significantly.
Exploiting Git and XML Nodes
The Git node is affected by CVE-2026-44790, enabling attackers to inject malicious command-line flags during Git push operations to access arbitrary files on the server. Classified under CWE-88, this flaw can expose sensitive information, including configuration files and credentials, potentially leading to full system compromise.
Another critical issue, CVE-2026-44791, pertains to the XML node. Despite previous patch efforts, attackers can still exploit prototype pollution through different paths, potentially leading to RCE when combined with other vulnerabilities.
Mitigation Measures and Recommendations
These vulnerabilities affect n8n versions below 1.123.43, 2.20.7, and 2.22.1, with patches available in these and subsequent versions. Immediate upgrades are strongly advised, as no complete workarounds are available.
For those unable to patch right away, restricting workflow editing permissions to trusted users and disabling vulnerable nodes via the NODES_EXCLUDE environment variable are recommended interim measures. However, these actions do not entirely eliminate the risk.
These security issues underscore a broader challenge within automation platforms like n8n, where the interconnectedness of nodes can inadvertently magnify the impact of individual vulnerabilities. Organizations utilizing n8n for essential automation tasks should prioritize these disclosures and implement prompt remediation to prevent potential exploits.
