CVE-2026-25053: n8n is Vulnerable to OS Command Injection in Git Node
Impact
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.
Patches
The issue has been fixed in n8n versions 2.5.0, and 1.123.10. Users should upgrade to this version or later to remediate the vulnerability.
Workarounds
If upgrading is not immediately possible, administrators should 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 not essential for operations. - Deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Resources
- n8n Documentation — Blocking nodes — how to globally disable specific nodes
---
n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backward compatibility.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Other sources
n8n is 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. This issue has been patched in versions 1.123.10 and 2.5.0.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-25053?
CVE-2026-25053 has a critical severity rating due to its potential for arbitrary command execution.
How do I fix CVE-2026-25053?
To fix CVE-2026-25053, update n8n to version 1.123.10 or 2.5.0 or later.
Who is affected by CVE-2026-25053?
CVE-2026-25053 affects authenticated users of n8n who have permissions to create or modify workflows.
What are the implications of CVE-2026-25053?
The implications of CVE-2026-25053 include the possibility for attackers to execute arbitrary commands and access sensitive files.
Was CVE-2026-25053 exploited in the wild?
As of the current information available, there are no confirmed reports of CVE-2026-25053 being exploited in the wild.