Which versions of n8n are affected by CVE-2026-72770?

n8n's Git node contains a path traversal vulnerability (CVE-2026-72770) allowing authenticated users to access arbitrary git repositories and their full commit history, potentially exposing…. A patch is available.

How to fix or mitigate CVE-2026-72770?

Within 24 hours, audit n8n instances to identify all users with workflow create and execute rights, and document current Git node usage in active workflows. Within 7 days, restrict workflow creation permissions to trusted users only, disable Git node functionality if not operationally critical, and scan accessible git repositories for exposed credentials that require rotation. Within 30 days, monitor vendor release channels for patched versions 1.123.67, 2.31.5, and 2.32.1; establish a testing plan and deploy patches to all environments immediately upon release.

n8n CVE-2026-72770

Q: What is the CVSS score of CVE-2026-72770?

CVE-2026-72770 has a CVSS 4.0 base score of 7.1 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.5%.

EUVD-2026-56096 HIGH

Path Traversal (CWE-22)

2026-08-11 VulnCheck

GHSA-vx5x-2g22-wqjr

Path Traversal N8n N8N Io

7.1

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

7.1 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

6.5 MEDIUM

Network-accessible by any low-privilege authenticated user; no integrity or availability impact; no scope change beyond the n8n process boundary.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Aug 11, 2026 - 13:17 EUVD

Source Code Evidence Fetched

Aug 11, 2026 - 12:53 vuln.today

Analysis Generated

Aug 11, 2026 - 12:53 vuln.today

CVE Published

Aug 11, 2026 - 12:17 cve.org

HIGH 7.1

DescriptionCVE.org

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.

AnalysisAI

Path traversal in n8n's Git node before versions 1.123.67, 2.31.5, and 2.32.1 allows authenticated low-privilege users to escape the repository sandbox during fetch, pull, and push-tags operations. By pointing an allowlisted remote configuration value at a local filesystem path outside the intended sandbox, an attacker with workflow create/execute rights can pull arbitrary local git repositories into the workspace and read their files and full commit history, including any secrets or credentials stored in git history. No public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV, but the low complexity and low-privilege attack path make it a realistic insider or compromised-account threat in multi-user n8n deployments.

Technical ContextAI

n8n is an open-source workflow automation platform distributed as the npm package n8n-io/n8n (CPE: cpe:2.3:a:n8n-io:n8n). Its Git node exposes git operations - clone, push, fetch, pull, and push-tags - as workflow steps. The existing sandbox path containment checks had already been applied to clone and push, but were not consistently enforced on the fetch, pull, and push-tags code paths, creating an asymmetric security boundary. The root cause is CWE-22 (Improper Limitation of a Pathname to a Restricted Directory - Path Traversal): by supplying a remote configuration value that resolves to a local filesystem path rather than a legitimate remote URL, the git operations treat an out-of-sandbox local directory as a remote repository and retrieve its contents. The fix is in commit f69dfc6dd2178a14ea1624d2e1d403c2e755042f, which extends the containment checks to the previously unprotected operations.

RemediationAI

The primary fix is to upgrade n8n to a patched release: version 1.123.67 for users on the 1.x branch, version 2.31.5 for users on 2.x before 2.32.0, or version 2.32.1 for users on 2.32.0. The upstream patch commit is f69dfc6dd2178a14ea1624d2e1d403c2e755042f, as documented in the advisory at https://github.com/n8n-io/n8n/security/advisories/GHSA-gf29-4f56-r2jf. If immediate upgrade is not feasible, the vendor offers two temporary workarounds: (1) Restrict n8n instance access exclusively to fully trusted users, eliminating the low-privilege threat actor - note this does not fix the vulnerability and any future account compromise reintroduces the risk. (2) Disable the Git node entirely by adding n8n-nodes-base.git to the NODES_EXCLUDE environment variable - this fully removes the vulnerable code path but also disables all Git-based workflow steps for all users. The vendor explicitly states neither workaround fully remediates the risk; they are short-term measures only.