https://feed.craftedsignal.io/products/n8n--2.21.0--2.22.1/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioThu, 14 May 2026 16:23:03 +0000https://feed.craftedsignal.io/briefs/2026-05-n8n-file-read/Thu, 14 May 2026 16:23:03 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-05-n8n-file-read/An authenticated user with workflow creation or modification permissions can inject CLI flags into the Git node's Push operation, leading to arbitrary file read on the n8n server; patched in versions 1.123.43, 2.20.7, and 2.22.1, and tracked as CVE-2026-44790.A critical vulnerability, CVE-2026-44790, exists within the n8n workflow automation platform. The vulnerability resides in the Git node’s Push operation, where an authenticated user with permissions to create or modify workflows can inject arbitrary CLI flags. This injection allows the attacker to read arbitrary files from the n8n server’s file system. Successful exploitation can lead to complete compromise of the n8n instance, including access to sensitive data stored on the server, such as credentials, API keys, and internal configuration files. Patches have been released in n8n versions 1.123.43, 2.20.7, and 2.22.1 to address this vulnerability.

Attack Chain

1. An attacker gains authenticated access to an n8n instance.
2. The attacker obtains permissions to create or modify workflows within n8n.
3. The attacker creates or modifies a workflow to include the Git node.
4. Within the Git node’s configuration, specifically the Push operation, the attacker injects malicious CLI flags. These flags are crafted to read arbitrary files from the server’s file system (e.g., using git --help).
5. The workflow is executed, and the Git node attempts to perform the Push operation with the injected flags.
6. Due to the flag injection, the Git command executes with the attacker-supplied arguments.
7. The attacker retrieves the contents of the targeted file, which may contain sensitive information.
8. The attacker leverages the stolen information to further compromise the n8n instance or connected systems.

Impact

Successful exploitation of CVE-2026-44790 allows an attacker to read arbitrary files from the n8n server. This can expose sensitive information such as API keys, credentials, configuration files, and other internal data. A successful attack could lead to full compromise of the n8n instance and potentially impact connected systems and data. The severity of the impact is critical due to the potential for complete system takeover and sensitive data exposure.

Recommendation

• Upgrade n8n to version 1.123.43, 2.20.7, 2.22.1, or later to patch CVE-2026-44790 as mentioned in the advisory.
• Limit workflow creation and editing permissions to only fully trusted users as a short-term workaround.
• Deploy the Sigma rule Detect n8n Git Node CLI Injection to identify potential exploitation attempts by monitoring process execution with suspicious Git commands.
• Monitor n8n application logs for Git node operations involving unusual command-line arguments, focusing on commands that attempt to read files outside the intended Git repository.

]]>criticaladvisoryarbitrary file readn8ngit nodeCVE-2026-44790https://feed.craftedsignal.io/briefs/2026-05-n8n-xml-prototype-bypass/Thu, 14 May 2026 16:22:47 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-05-n8n-xml-prototype-bypass/An authenticated n8n user with workflow creation privileges can bypass a previous patch for XML node prototype pollution, potentially leading to remote code execution on the n8n host when combined with other nodes; patched in versions 1.123.43, 2.20.7, and 2.22.1.An authenticated user with permission to create or modify workflows can bypass the patch for GHSA-hqr4-h3xv-9m3r in the XML node of n8n, a workflow automation platform. This vulnerability, identified as CVE-2026-44791, allows for prototype pollution. Successful exploitation, when chained with other nodes, can lead to remote code execution (RCE) on the n8n host. The affected versions include n8n versions prior to 1.123.43, versions 2.21.0 to 2.22.1 (excluding 2.22.1), and versions 2.0.0-rc.0 to 2.20.7 (excluding 2.20.7). This vulnerability matters to defenders because it allows attackers to gain complete control over the n8n instance, potentially compromising sensitive data and enabling further malicious activities.

Attack Chain

1. An attacker gains authenticated access to an n8n instance with workflow creation and modification privileges.
2. The attacker crafts a malicious workflow that includes the XML node.
3. The attacker exploits CVE-2026-44791, bypassing the patch for GHSA-hqr4-h3xv-9m3r by manipulating XML node parameters to inject a prototype pollution payload.
4. The prototype pollution modifies JavaScript object prototypes within the n8n environment.
5. The attacker chains the XML node with other nodes in the workflow (e.g., Function node, Execute Command node).
6. The polluted prototypes are leveraged by the subsequent nodes to execute arbitrary JavaScript code.
7. The arbitrary code execution allows the attacker to execute system commands on the n8n host.
8. The attacker achieves remote code execution (RCE), gaining control of the n8n host and potentially compromising the underlying system.

Impact

Successful exploitation of CVE-2026-44791 allows an attacker to achieve remote code execution on the n8n host. This could lead to the complete compromise of the n8n instance, potentially affecting all workflows and data managed by the platform. The attacker could potentially access sensitive information, modify workflows for malicious purposes, or use the compromised host as a pivot point for further attacks within the network. The vulnerability affects n8n instances running vulnerable versions prior to the patched versions, impacting any organization using n8n for workflow automation.

Recommendation

• Upgrade n8n to version 1.123.43, 2.20.7, or 2.22.1 or later to remediate CVE-2026-44791, as mentioned in the overview.
• Deploy the Sigma rule “Detect n8n XML Node Prototype Pollution Attempt” to identify suspicious workflow creations involving the XML node, as described in the rules section.
• If immediate upgrade is not possible, implement the suggested workarounds by limiting workflow creation/editing permissions or disabling the XML node via the NODES_EXCLUDE environment variable, as detailed in the overview section.

]]>criticaladvisoryprototype pollutionRCEn8nCVE-2026-44791