Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
Check your stack
CVE-2026-92587medium5.3

n8n before 1.123.76 Sandbox Escape via Git Relative URL

Impact

n8n workflow automation platform versions before 1.123.76, 2.37.7, and 2.38.2 have a sandbox escape vulnerability via Git relative URL. An authenticated user can make an identical URL string pass the file-access check, allowing access to a git repository outside the sandbox. This can lead to reading contents of the repository.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

n8n-io · VulnCheck

n8n

2 ranges

Package identity

pkg:npm/n8nExplore n8n →

Identity supplied by VulnCheck. Version matching requires compatible range evidence.

Compare with this publisher’s ranges. This does not inspect your installation.

affected

0 → before 1.123.76

semver versions

unaffected

1.123.76

semver versions

unknown

Other versions: unaffected

n8n-io · VulnCheck

n8n

2 ranges

Package identity

pkg:npm/n8nExplore n8n →

Identity supplied by VulnCheck. Version matching requires compatible range evidence.

Compare with this publisher’s ranges. This does not inspect your installation.

affected

2.38.0 → before 2.38.2

semver versions

unaffected

2.38.2

semver versions

unknown

Other versions: unaffected

n8n-io · VulnCheck

n8n

2 ranges

Package identity

pkg:npm/n8nExplore n8n →

Identity supplied by VulnCheck. Version matching requires compatible range evidence.

Compare with this publisher’s ranges. This does not inspect your installation.

affected

2.0.0-rc.0 → before 2.37.7

semver versions

unaffected

2.37.7

semver versions

unknown

Other versions: unaffected

Original 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.

Inside the record

Evidence available

Package identity
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-92587

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-426 ↗

Untrusted Search Path

VulnCheck

Related →

Environment requirements

These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.

VulnCheck · platform conditions

Any condition may hold

Vulnerable product

cpe:2.3:a:n8n:n8n:*:*:*:*:*:*:*:*

Before: 1.123.76

Any condition may hold

Vulnerable product

cpe:2.3:a:n8n:n8n:*:*:*:*:*:*:*:*

From (inclusive): 2.38.0

Before: 2.38.2

Any condition may hold

Vulnerable product

cpe:2.3:a:n8n:n8n:*:*:*:*:*:*:*:*

From (inclusive): 2.0.0-rc.0

Before: 2.37.7

Original applicability statements
[
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:a:n8n:n8n:*:*:*:*:*:*:*:*",
            "versionEndExcluding": "1.123.76"
          }
        ]
      }
    ]
  },
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:a:n8n:n8n:*:*:*:*:*:*:*:*",
            "versionEndExcluding": "2.38.2",
            "versionStartIncluding": "2.38.0"
          }
        ]
      }
    ]
  },
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:a:n8n:n8n:*:*:*:*:*:*:*:*",
            "versionEndExcluding": "2.37.7",
            "versionStartIncluding": "2.0.0-rc.0"
          }
        ]
      }
    ]
  }
]
Contributing organizations · 2
VulnCheck

Assigning organization

2026-10-29
CISA-ADP

Additional data publisher

2026-09-21

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

2 sources