Introduction
Attackers can execute arbitrary code on n8n servers by abusing a workflow automation feature that works with git repositories. The flaw puts the credentials, workflow logic, and third-party integrations that n8n manages directly at risk. Organizations that use n8n for process automation, in the cloud or self-hosted, should review their deployments immediately.
n8n is an open source workflow automation platform with over 400 integrations and a rapidly growing user base. Technical teams use it widely to automate business processes, data flows, and integrations with cloud and SaaS services. It runs as a managed cloud service or self-hosted, so the issue is relevant to a broad range of organizations.
Technical Information
CVE-2025-62726 is a remote code execution vulnerability in the Git Node component of n8n. The Git Node lets workflows run git operations such as clone, commit, and push. The problem starts when a user clones a remote repository that contains a malicious pre-commit hook in its .git/hooks directory. If the workflow then commits with the Git Node, the malicious hook runs with the privileges of the n8n process.
The root cause is insufficient isolation of git hook execution within the n8n environment. Cloning a repository copies all of its files, including hooks, and git runs any pre-commit hook it finds during a commit. In n8n, that means attacker-controlled code can run inside the workflow automation environment, where it could access credentials, modify workflows, or interact with integrated systems. The vulnerability is classified as CWE-829 (Inclusion of Functionality from Untrusted Control Sphere).
No public code snippets are available for this vulnerability. The issue is confirmed and fixed in n8n version 1.113.0.
Affected Systems and Versions
- Product: n8n (workflow automation platform)
- Affected component: Git Node
- Deployment models: Cloud and Self-Hosted
- Version range: All versions prior to 1.113.0
- Fixed in: 1.113.0 and later
Vendor Security History
n8n has previously disclosed vulnerabilities in several core components:
- Stored XSS in Form Trigger node (GHSA-hfmv-hhh3-43f2)
- Improper authorization in workflow execution stop endpoint (GHSA-gq57-v332-7666)
- Arbitrary command execution in Execute Command node (GHSA-365g-vjw2-grx8)
- Symlink traversal in Read/Write File node (GHSA-ggjm-f3g4-rwmm)
The vendor maintains a public security advisory page and has patched issues in reasonable time. The number and variety of these vulnerabilities, though, point to a need for stronger security testing and architectural changes.
