CVE-2026-49465
Awaiting Analysis Awaiting Analysis - Queue
Path Traversal in n8n Workflow Automation

Publication date: 2026-06-23

Last updated on: 2026-06-23

Assigner: GitHub, Inc.

Description
n8n is an open source workflow automation platform. Prior to 1.123.48, 2.21.8, and 2.22.4, 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. This vulnerability is fixed in 1.123.48, 2.21.8, and 2.22.4.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-23
Last Modified
2026-06-23
Generated
2026-06-23
AI Q&A
2026-06-23
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
n8n n8n to 2.22.4 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-49465 is a vulnerability in n8n, an open-source workflow automation platform. It allows an authenticated user who has permission to create or modify workflows to bypass file sandbox restrictions by supplying a local filesystem path as the source repository in the Git node's Clone operation or as the target repository in the Push operation.

This bypass lets the user read the contents of any local Git repository accessible to the n8n process, circumventing the N8N_RESTRICT_FILE_ACCESS_TO sandbox that normally blocks direct file reads to restricted paths.

The vulnerability affects n8n versions prior to 1.123.48, 2.21.8, and 2.22.4, and has been fixed in these versions.

Impact Analysis

This vulnerability can impact you by allowing an attacker with workflow creation or modification permissions to read sensitive data stored in any local Git repository accessible to the n8n process.

Since the vulnerability bypasses file access restrictions, it can lead to unauthorized disclosure of confidential information.

The CVSS score is 6.0 (Moderate), indicating a significant impact on confidentiality, but no impact on integrity or availability.

Detection Guidance

Detection of this vulnerability involves identifying whether an authenticated user with workflow creation or modification permissions is supplying local filesystem paths in the Git node's Clone or Push operations to bypass sandbox restrictions.

Since the vulnerability exploits the use of local filesystem paths in Git node operations, monitoring logs for unusual Git clone or push commands referencing local paths could help detect exploitation attempts.

There are no specific commands provided in the available resources to detect this vulnerability directly.

Mitigation Strategies

Immediate mitigation steps include upgrading n8n to versions 1.123.48, 2.21.8, or 2.22.4 where the vulnerability is fixed.

As a temporary measure before upgrading, restrict workflow creation and modification permissions to trusted users only.

Alternatively, disable the Git node entirely to prevent exploitation of this vulnerability.

Compliance Impact

This vulnerability allows an authenticated user with certain permissions to bypass file sandbox restrictions and read the contents of any local Git repository accessible to the n8n process. This results in a high impact on confidentiality.

Since confidentiality of data is a critical aspect of compliance with standards like GDPR and HIPAA, this vulnerability could lead to unauthorized access to sensitive information, potentially causing non-compliance with these regulations.

Mitigations such as upgrading to patched versions or restricting workflow permissions are necessary to maintain compliance and protect sensitive data.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-49465. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart