CVE-2026-25053 Overview
CVE-2026-25053 is a critical command injection vulnerability affecting n8n, an open source workflow automation platform. Prior to versions 1.123.10 and 2.5.0, vulnerabilities in the Git node allowed authenticated users with permission to create or modify workflows to execute arbitrary system commands or read arbitrary files on the n8n host.
Critical Impact
Authenticated attackers can achieve remote code execution and arbitrary file read on the n8n host system through the vulnerable Git node, potentially leading to complete system compromise.
Affected Products
- n8n versions prior to 1.123.10
- n8n versions prior to 2.5.0
- n8n workflow automation platform (Node.js)
Discovery Timeline
- 2026-02-04 - CVE-2026-25053 published to NVD
- 2026-02-05 - Last updated in NVD database
Technical Details for CVE-2026-25053
Vulnerability Analysis
This vulnerability is classified as CWE-78 (Improper Neutralization of Special Elements used in an OS Command), commonly known as OS Command Injection. The flaw exists within the Git node functionality of the n8n workflow automation platform.
When an authenticated user with workflow creation or modification permissions interacts with the Git node, the application fails to properly sanitize user-supplied input before passing it to underlying system commands. This allows attackers to inject malicious commands that execute with the privileges of the n8n process on the host system.
The vulnerability enables two primary attack scenarios: arbitrary command execution, where attackers can run any system command on the host, and arbitrary file read, allowing sensitive data exfiltration from the server filesystem.
Root Cause
The root cause of this vulnerability stems from insufficient input validation and sanitization within the Git node implementation. When processing Git-related operations, user-controlled parameters are passed directly to shell commands without proper escaping or validation. This allows attackers to break out of the intended command context and inject additional malicious commands.
Attack Vector
The attack vector is network-based, requiring authentication but no user interaction. An attacker must have valid credentials with permissions to create or modify workflows in the n8n platform. Once authenticated, the attacker can craft a malicious workflow leveraging the Git node to inject arbitrary commands.
The exploitation flow involves creating or modifying a workflow that utilizes the Git node with specially crafted parameters containing shell metacharacters or command separators. When the workflow executes, the injected commands run on the underlying host system with the privileges of the n8n service account.
Due to the sensitive nature of this vulnerability, specific exploitation code is not provided. Refer to the GitHub Security Advisory for additional technical details.
Detection Methods for CVE-2026-25053
Indicators of Compromise
- Unusual Git-related process spawning from the n8n service
- Unexpected shell command execution originating from the n8n Node.js process
- Anomalous file access patterns, particularly attempts to read sensitive system files like /etc/passwd or credential files
- Workflows containing suspicious Git node configurations with shell metacharacters
Detection Strategies
- Monitor process creation events from the n8n service for unexpected child processes
- Implement application-level logging to capture Git node parameter values
- Deploy endpoint detection solutions to identify command injection patterns
- Review workflow definitions for malicious or suspicious Git node configurations
Monitoring Recommendations
- Enable verbose logging for the n8n application to capture workflow execution details
- Monitor network connections initiated by the n8n process for potential data exfiltration
- Implement file integrity monitoring on the n8n host system
- Set up alerts for unusual CPU or memory usage patterns that may indicate exploitation
How to Mitigate CVE-2026-25053
Immediate Actions Required
- Upgrade n8n to version 1.123.10 or 2.5.0 or later immediately
- Audit existing workflows for potentially malicious Git node configurations
- Review and restrict user permissions for workflow creation and modification
- Implement network segmentation to limit the blast radius of potential compromise
Patch Information
The n8n development team has addressed this vulnerability in versions 1.123.10 and 2.5.0. Organizations running affected versions should prioritize upgrading to these patched releases. For detailed patch information, refer to the GitHub Security Advisory GHSA-9g95-qf3f-ggrw.
Workarounds
- Temporarily disable the Git node functionality if not required for business operations
- Restrict workflow creation and modification permissions to trusted administrators only
- Implement additional network-level controls to limit outbound connections from the n8n host
- Deploy a web application firewall to inspect and block potentially malicious requests
# Example: Upgrading n8n using npm
npm update [email protected]
# Or for version 2.x
npm update [email protected]
# Verify the installed version
n8n --version
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
