CVE-2026-25053 is a critical flaw (CVSS 9.9) in n8n, the workflow automation platform. Weaknesses in the Git node let a user who can create or edit workflows run system commands or read arbitrary files on the host. n8n 1.123.10 and 2.5.0 fix it, so upgrade and restrict the Git node until then.
What's affected
- Affected: n8n before 1.123.10 on 1.x, and before 2.5.0 on 2.x.
- Fixed in: 1.123.10 and 2.5.0.
- Who can trigger it: authenticated users with permission to create or modify workflows.
Note the difference from its sibling advisories. This fix landed in an earlier 1.x release, 1.123.10, while the related file read and expression fixes need 1.123.18 and 1.123.17. If you are on 1.x, move to the highest of the fixed versions, not the lowest.
How to check if you're exposed
Check your n8n version, then check whether any workflow uses the Git node.
docker ps --format '{{.Image}}' | grep n8n
In the editor, search your workflows for the Git node. If you do not use it, you can block it globally, which n8n's documentation describes under blocking nodes. Also review who holds workflow edit rights. Each such account is a possible route to the host.
What to do now
- Upgrade to n8n 1.123.10 or later on 1.x, or 2.5.0 or later on 2.x. Prefer 1.123.18 or later, to cover the sibling advisories.
- Limit workflow creation and editing to fully trusted users.
- Restrict or disable the Git node if you do not need it.
- Run n8n in a hardened environment with limited operating system privileges and network access.
- Treat these workarounds as stopgaps. The advisory says they do not fully remediate the risk.
Why it matters
The weakness is CWE-78 (OS Command Injection), OS command injection. A node that shells out to run Git has to treat every parameter as untrusted. If a parameter can change the command that runs, the author of the workflow controls the host.
Several n8n advisories landed together. That is a reason to review your whole n8n setup, not only this one CVE. Use a single upgrade to clear them together.
Quick check
Is this exploited in the wild?
The record does not mark it as a CISA Known Exploited Vulnerability, and the advisory does not report exploitation.
Can I just disable the Git node?
The advisory lists that as a temporary mitigation if you do not need the node, together with limiting editor access. It still recommends upgrading.
Sources
Last reviewed: 19 October 2026.
