PT-2026-50151 · Npm · N8N

Published 2026-06-16 · Updated 2026-06-16 · CVE-2026-49465

OSV

CVSS v3.1

7.7

High

Base vector

AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

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.

Fix

Path traversal

Weakness Enumeration

CWE-22

Related Identifiers

CVE-2026-49465

GHSA-5XP3-2W67-427V

Affected Products

N8N

References · 3

• https://osv.dev/vulnerability/GHSA-5xp3-2w67-427v · Vendor Advisory
• https://github.com/n8n-io/n8n/security/advisories/GHSA-5xp3-2w67-427v · Note
• https://github.com/n8n-io/n8n · Note