n8n flaws widen automation security risk

Critical security flaws in n8n have exposed how quickly workflow automation platforms can become high-value targets when they connect business systems, credentials, data stores and artificial intelligence tools inside one operating layer.

The vulnerabilities affect n8n versions before 1.123.43, 2.20.7 and 2.22.1, with security advisories warning that attackers with workflow creation or modification rights could combine weaknesses to achieve remote code execution on affected servers. The most serious issues carry critical severity ratings and could allow compromise of the host running the automation service, depending on how the platform has been configured and exposed.

n8n is widely used by technical teams to build automated workflows across cloud services, APIs, databases, messaging platforms and AI systems. Its appeal lies in a hybrid model that combines visual workflow design with code-level flexibility, allowing organisations to self-host the software or use a managed cloud service. That same flexibility has increased the security stakes, as workflows often handle secrets, authentication tokens, customer data and privileged connections to internal systems.

One disclosed flaw involves the HTTP Request node, where an unvalidated pagination parameter could allow prototype pollution. A user with permissions to create or edit workflows could abuse the weakness and, when combined with other techniques, reach remote code execution. The vulnerability has been rated 9.4 on the CVSS scale, reflecting network exploitability, low attack complexity and high potential impact on confidentiality, integrity and availability.

Another critical issue affects the Git node’s Push operation. Attackers with workflow-editing privileges could inject command-line flags, enabling arbitrary file reads from the n8n server. That could expose configuration files, stored secrets, environment variables or other sensitive material, creating a path towards full compromise. The affected versions span older 1. x releases, parts of the 2.0 release candidate line and the 2.21 branch before the fixed versions.

Additional advisories linked to the same patch cycle identify weaknesses involving dynamic credential OAuth endpoints, source control pull operations, SQL injection risks in internal data-table handling, and a bypass of an earlier XML node prototype pollution patch. Taken together, the vulnerabilities underline a broader problem for automation tools: a flaw in one node or integration can be amplified by the platform’s ability to orchestrate actions across many connected services.

The risk is especially acute in self-hosted deployments, where administrators control patching, exposure and user permissions. n8n Cloud instances have been handled separately by the vendor, while self-managed users have been urged to upgrade to fixed releases. Temporary mitigations include restricting workflow creation and editing rights to trusted users only, disabling vulnerable nodes through the NODES_EXCLUDE environment variable, and reviewing source control integrations. These measures reduce exposure but do not replace patching.

Security teams are likely to treat the n8n flaws as more than a routine application update because automation platforms increasingly sit close to business-critical data flows. A compromised instance could allow attackers to harvest credentials, manipulate workflows, access third-party services, run malicious code, move laterally across connected systems or disrupt automated operations. Where n8n is used for AI data ingestion, customer support routing, finance operations or DevOps processes, the blast radius can extend well beyond the original server.

The disclosures follow a series of n8n security issues over the past several months, including sandbox escapes, expression evaluation flaws and unauthenticated remote code execution weaknesses affecting earlier versions. Several of those bugs centred on the difficulty of safely executing user-controlled logic inside a platform designed to let users automate complex tasks. The pattern has raised scrutiny of how low-code and no-code platforms enforce isolation between user workflows and the underlying runtime.

n8n’s rapid adoption has made that scrutiny more important. The project has attracted a large developer community, extensive GitHub attention and significant venture backing as demand grows for AI-enabled workflow orchestration. Its integrations with hundreds of services make it useful for teams seeking control over data and automation, but each integration also expands the attack surface if permissions, secrets and execution environments are not tightly managed.