CVE-2026-72770
mediumpriority · track · 26EPSS 0.007 · 53 %ileDEEUUSEPSS · scored 2026-10-26
n8n versions before 1.123.67 contain a path traversal vulnerability in the Git node's fetch, pull, and push-tags operations that allows authenticated users to bypass repository-path containment checks. Attackers with workflow create/execute rights can point allowlisted remote configurations at local paths outside the sandbox to pull arbitrary git repositories and read their files and history.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 4.9–7.1
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (15)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2026-2489n8n: Mehrere SchwachstellenDeutsch2026-07-22csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in n8n ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen SQL-Injection Angriff durchzuführen, und um beliebigen Programmcode auszuführen.
- GHSA-gf29-4f56-r2jfn8n: Git Node fetch/pull/pushTags Operations Bypass Sandbox Path Restriction2026-07-22ghsa · osvUS
## Impact Authenticated n8n users with workflow create/execute rights could use the Git node's fetch, pull, or push-tags operations to bypass the repository-path containment checks that already protected clone and push. By pointing an allowlisted remote configuration value at a local path outside the intended sandbox, an attacker could pull an arbitrary local git repository into the workspace and subsequently read its files and history. ## Patches The issue has been fixed in n8n versions 1.123.67, 2.31.5, and 2.32.1. Users should upgrade to one of these versions or later to remediate the vulnerability. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict n8n instance access to fully trusted users only. - Disable the Git node by adding `n8n-nodes-base.git` to the `NODES_EXCLUDE` environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (6)
External citations — patches, advisories, analysis.
- https://github.com/n8n-io/n8n/security/advisories/GHSA-gf29-4f56-r2jfcnnvd
- https://www.vulncheck.com/advisories/n8n-before-path-traversal-via-git-node-operationscnnvd
- https://github.com/n8n-io/n8n/security/advisories/GHSA-gf29-4f56-r2jfenisa_euvd
- https://www.vulncheck.com/advisories/n8n-before-path-traversal-via-git-node-operationsenisa_euvd
- https://github.com/n8n-io/n8n/security/advisories/GHSA-gf29-4f56-r2jfMitigationVendor Advisorynvd
- https://www.vulncheck.com/advisories/n8n-before-path-traversal-via-git-node-operationsThird Party Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan