CVE-2026-25053: n8n Git Node OS Command Injection Vulnerability
Summary
CVE-2026-25053: n8n has OS Command Injection in Git Node. Affects n8n across 2 version ranges.
< 1.123.10
>= 2.0.0, < 2.5.0
Fixed in 1.123.10 or 2.5.0, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
n8n is an open-source workflow automation tool that allows users to connect various applications and services to automate tasks. It provides a user-friendly interface for creating workflows that can integrate with APIs, databases, and other services. However, a critical vulnerability has been identified in the Git node of n8n, which could allow unauthorized command execution on the host system.
Vulnerability Detail
The vulnerability arises from improper handling of user inputs in the Git node, allowing authenticated users with permissions to create or modify workflows to execute arbitrary system commands or read sensitive files on the n8n host. This could lead to severe security breaches, including unauthorized access to system resources and data leakage.
How To Fix
Latest published version: 2.44.6 as of 22 Oct 2026
npm install n8n@2.44.6Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 1.123.101.123.10npm install n8n@1.123.10 -
>= 2.0.0, < 2.5.02.5.0npm install n8n@2.5.0
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
If immediate upgrading is not feasible, consider the following temporary mitigations:
- Limit workflow creation and editing permissions to fully trusted users only.
- Restrict or disable access to the Git node if it is not essential for operations.
- Deploy n8n in a hardened environment with restricted operating system privileges and network access to minimize the impact of potential exploitation.
Conclusion
The n8n Git node vulnerability (CVE-2026-25053) poses a critical risk by allowing command injection through improperly handled user inputs. It is essential for users to upgrade to the patched versions to secure their systems. Temporary workarounds can help mitigate risks until an upgrade is possible.
See every vulnerability recorded for n8n →
FAQ
The CVSS score of this vulnerability is 9.4, indicating a critical level of severity.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
The potential risks include unauthorized command execution, data leakage, and severe security breaches on the host system.
Yes, you can limit permissions for workflow creation and editing, restrict access to the Git node, and deploy n8n in a more secure environment.
Versions 2.5.0 and later, as well as 1.123.10 and later, have patched this vulnerability.
References
Related vulnerabilities
Recent vulnerabilities recorded for n8n.
