n8n: Git Node fetch/pull/pushTags Operations Bypass Sandbox Path Restriction
n8n
- Severity
- High, CVSS 7.1
- 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
- Record
- GHSA-gf29-4f56-r2jf
- Affects
- n8n
- Known exploited
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- Record first published by the source
- July 22, 2026
- Source last modified
- July 22, 2026
Description
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.
Description quoted from the GitHub Advisory Database.
Who is affected
n8n is a platform for automating work by linking apps and services into step-by-step workflows. This flaw affects the Git building block, which lets a workflow copy and update files kept in Git (a common system for tracking files and their history), in copies of n8n not yet updated to a fixed version. A signed-in user who is allowed to create or run workflows could use its fetch, pull or push tags actions to bring in a Git collection of files stored elsewhere on the same server, outside the area n8n is meant to use, and then read its files and history. This flaw is rated High.
What to do
- The person who installed or runs n8n, or the IT provider who manages it for your organization, should handle this.
- Upgrade n8n to version
1.123.67,2.31.5or2.32.1, or a later version. - If you cannot upgrade right away, limit access to your n8n to fully trusted users only, and turn off the Git building block by adding
n8n-nodes-base.gitto theNODES_EXCLUDEenvironment variable (a server setting). These steps do not fully remove the risk and should only be used for a short time. - If an IT provider or vendor runs n8n for you, send them this advisory and ask when the update will be done.
Analysis written from the source record as of July 22, 2026 and reviewed before publishing.