CVE-2026-92587: n8n before 1.123.76 Sandbox Escape via Git Relative URL
n8n is a workflow automation platform. In versions before 1.123.76, 2.37.7, and 2.38.2, the Git node validated a relative remote URL against the configured repositoryPath but then invoked git with that path as its working directory; git walked up to the enclosing repository's top level and resolved the same relative URL from there. An authenticated user (member) who nested the repository one level below the configured path could therefore make an identical URL string pass the file-access check while git resolved it outside the sandbox. A subsequent fetch or pull read a git repository outside N8NRESTRICTFILEACCESSTO and merged its objects into the user's own repository, where their contents could be read back. The issue is fixed in n8n 1.123.76, 2.37.7, and 2.38.2, which resolve the remote reference from the directory git actually operates in before applying the sandbox check. As a workaround, the Git node can be disabled by adding n8n-nodes-base.git to NODESEXCLUDE.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 1.123.76 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.37.7 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.38.2 - Configuration
As a workaround prior to the fixed versions, disable the Git node by adding 'n8n-nodes-base.git' to NODES_EXCLUDE.
n8n configuration NODES_EXCLUDE = n8n-nodes-base.git
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated n8n user with the member role can exploit it. They must be able to use the Git node and arrange for a repository to be nested one level below the configured repositoryPath.
What data can be exposed?
The attacker can cause a fetch or pull to read a Git repository outside N8N_RESTRICT_FILE_ACCESS_TO and merge its objects into their own repository. They can then read the imported repository contents back from their repository.
Are default deployments affected?
The issue concerns deployments using the Git node with N8N_RESTRICT_FILE_ACCESS_TO as the file-access sandbox boundary. The provided information does not establish whether that setting is enabled by default.
What can be done if upgrading is not immediately possible?
Disable the Git node by adding n8n-nodes-base.git to NODES_EXCLUDE. This removes the vulnerable Git-node functionality until an update can be applied.
Which releases contain the fix?
The issue is fixed in n8n 1.123.76, 2.37.7, and 2.38.2. The fix resolves the remote reference from Git's actual working directory before enforcing the sandbox check.