CVE-2026-92587

n8n before 1.123.76 Sandbox Escape via Git Relative URL

MEDIUM
5
CVSS Score
Published: September 16, 2026 at 09:46 PM UTC
Updated: October 29, 2026 at 09:17 PM UTC
2 products affected across 2 vendorsN8NN8N

Using n8n by n8n-io?

Get instant alerts when new vulnerabilities affect n8n - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

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 N8N_RESTRICT_FILE_ACCESS_TO 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 NODES_EXCLUDE.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

95%
v < 1.123.76v < 2.37.7v < 2.38.2
Affected range stops below 1.123.76, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.37.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.38.2, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 1.123.76 (unaffected)
Vendor states this is fixed in 2.37.7 (unaffected)
Vendor states this is fixed in 2.38.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5MEDIUMVulnCheck
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
CHANGED
Confidentiality
LOW
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-426

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card