CVE-2026-72770 Overview
CVE-2026-72770 is a path traversal vulnerability [CWE-22] in n8n workflow automation platform versions before 1.123.67. The flaw resides in the Git node's fetch, pull, and push-tags operations, which fail to enforce repository-path containment. Authenticated users with workflow create or execute permissions can bypass sandbox restrictions by pointing allowlisted remote configurations at local paths. This enables attackers to pull arbitrary git repositories from the host filesystem and read their contents and commit history. The vulnerability affects n8n self-hosted deployments where workflow creation privileges are granted to lower-trust users.
Critical Impact
Authenticated users can read arbitrary git repositories and their history from the host filesystem, exposing source code, credentials committed to history, and internal configuration data.
Affected Products
- n8n versions prior to 1.123.67
- Self-hosted n8n deployments exposing the Git node
- Multi-tenant n8n instances with workflow editor access for lower-trust users
Discovery Timeline
- 2026-08-11 - CVE-2026-72770 published to NVD
- 2026-08-11 - Last updated in NVD database
Technical Details for CVE-2026-72770
Vulnerability Analysis
The vulnerability exists in n8n's Git node implementation, which provides workflow steps for interacting with git repositories. The node validates that repository paths remain inside a designated sandbox directory before executing git operations. However, the fetch, pull, and push-tags operations do not consistently apply this containment check when resolving remote configurations.
An attacker with permission to create or execute workflows constructs a Git node operation that references an allowlisted remote. The remote configuration is then redirected to point at a local filesystem path outside the sandbox. Because the containment logic is bypassed for these three operations, git executes against the attacker-chosen path.
The result is that git reads objects, refs, and history from repositories the attacker should not be able to access. Extracted data can include source code, hardcoded secrets, deployment keys, and prior commit history containing sensitive material.
Root Cause
The root cause is incomplete input validation on repository path resolution. The Git node's sandbox enforcement was applied inconsistently across operations, leaving fetch, pull, and push-tags unchecked. Attackers exploit this gap to traverse the filesystem via allowlisted-but-unvalidated remote configuration parameters.
Attack Vector
Exploitation requires an authenticated n8n account with workflow create or execute privileges. The attack is network-accessible through the standard n8n web interface or API. No user interaction from an administrator is required. The vulnerability manifests when the Git node is invoked with a crafted remote configuration that resolves to a local path.
Refer to the GitHub Security Advisory GHSA-gf29-4f56-r2jf and the VulnCheck Path Traversal Advisory for additional technical context.
Detection Methods for CVE-2026-72770
Indicators of Compromise
- Git node executions referencing unusual local filesystem paths such as /etc, /root, /home, or application data directories
- n8n audit log entries showing workflow modifications that alter Git node remote parameters shortly before execution
- Unexpected outbound git traffic or file reads originating from the n8n process user
- Workflow execution history containing fetch, pull, or push-tags operations against non-standard URLs or paths
Detection Strategies
- Inventory n8n instances and identify versions below 1.123.67 using package metadata or the /rest/settings endpoint
- Review workflow definitions in the n8n database for Git nodes whose remote parameters contain path traversal sequences or local filesystem prefixes
- Correlate authenticated n8n session activity with process-level file access telemetry on the host running n8n
Monitoring Recommendations
- Enable n8n audit logging and forward events to a centralized SIEM for retention and correlation
- Monitor filesystem read activity by the n8n process user against sensitive directories outside the expected workflow sandbox
- Alert on creation or modification of Git node workflows by non-administrator accounts
How to Mitigate CVE-2026-72770
Immediate Actions Required
- Upgrade all n8n instances to version 1.123.67 or later without delay
- Audit existing workflows for Git node usage and review remote configurations for suspicious local paths
- Rotate any secrets, deployment keys, or tokens that may have been exposed through repositories accessible on the n8n host
- Restrict workflow create and execute permissions to trusted users on shared or multi-tenant deployments
Patch Information
The fix is available in n8n 1.123.67. The patch enforces consistent repository-path containment across the fetch, pull, and push-tags operations. Consult the GitHub Security Advisory GHSA-gf29-4f56-r2jf for release details and upgrade notes.
Workarounds
- Disable or block the Git node in workflow templates until patching is complete
- Run the n8n process under a dedicated low-privilege service account with filesystem access limited to required directories
- Apply operating-system level access controls such as AppArmor, SELinux, or filesystem ACLs to prevent the n8n process from reading sensitive paths
- Remove workflow editor permissions from untrusted or lower-trust user roles until the upgrade is deployed
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
