n8n before 1.123.76 Sandbox Escape via Git Relative URL (CVE-2026-92587) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-92587

n8n before 1.123.76 Sandbox Escape via Git Relative URL

Answer in brief

CVE-2026-92587 records a Unknown severity vulnerability in n8n before 1.123.76 Sandbox Escape via Git Relative URL. The current sources do not mark it as known exploited. The current feed maps n8n-io/n8n (generic), n8n-io/n8n (generic), n8n-io/n8n (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 16, 2026Updated Sep 16, 2026Source checked Sep 17, 2026First seen by HOL Sep 16, 2026Material review Sep 16, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 3 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps n8n-io/n8n (generic), n8n-io/n8n (generic), n8n-io/n8n (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
n8n-io/n8ngeneric	>=0 <1.123.76	1.123.76
n8n-io/n8ngeneric	>=0 <2.38.2	2.38.2
n8n-io/n8ngeneric	>=0 <2.37.7	2.37.7

Recommended response

Check inventory. Check lockfiles and deployed manifests for n8n-io/n8n, n8n-io/n8n, n8n-io/n8n.
Review the reported fix. Update n8n-io/n8n to 1.123.76; n8n-io/n8n to 2.38.2; n8n-io/n8n to 2.37.7 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 16, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.