MISFIRE

Browse / AI Framework and Platform Flaws / CVE-2026-49465

n8n: Git Node Clone and Push Operations Bypass File Sandbox

CVE-2026-49465 ยท 2026-06-16 moderate

Class
AI Framework and Platform Flaws (filed by a model that read the source)
Technique
Path traversal and file access
Affected
n8n (npm)
Gets past
Path restriction
CVSS
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS
0.5% chance of exploitation in 30 days

How it works, in short

The Git node accepts local filesystem paths as clone or push sources, letting workflows copy repositories that the file sandbox would block. (Our summary, written by a model. The source text is below.)

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.

References

Source: GitHub Advisory Database, used under CC BY 4.0.