Advisory

GHSA-5xp3-2w67-427v

Also known as: CVE-2026-49465

Summary

n8n: Git Node Clone and Push Operations Bypass File Sandbox

Details

Impact
An authenticated user with permission to create or modify workflows could supply a local filesystem path as the source repository in the Git node's Clone operation, or as the target repository in the Push operation, bypassing the N8N_RESTRICT_FILE_ACCESS_TO file sandbox. This allowed the contents of any local git repository accessible to the n8n process to be cloned into an allowed path and read, circumventing the access restrictions that correctly blocked direct file reads to the same paths.

Patches
The issue has been fixed in n8n versions 1.123.48, 2.21.8, and 2.22.4. 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:

  • Limit workflow creation and editing permissions 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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-06-16 17:37 UTC
Modified
2026-07-20 14:00 UTC

Affected packages and fixes

n8n

npm · All systems

Affected

  • introduced 0, fixed 1.123.48 (semver)

Fixed versions

1.123.48

Fix

n8n

npm · All systems

Affected

  • introduced 2.22.0, fixed 2.22.4 (semver)

Fixed versions

2.22.4

Fix

n8n

npm · All systems

Affected

  • introduced 2.0.0-rc.0, fixed 2.21.8 (semver)

Fixed versions

2.21.8

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences