CVE-2026-49465
HighCVSS 7.7Exploitation Probability (EPSS)
Low risk39th percentile — higher than 39% of all known CVEs
Summary
In n8n before versions 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.
Risk Assessment
The risk involves unauthorized reading of sensitive data from local Git repositories, potentially leading to information disclosure such as source code, passwords, or access keys stored in repositories.
Recommendation
It is recommended to immediately update n8n to versions 1.123.48, 2.21.8, or 2.22.4, which contain a fix for this vulnerability.
Original NVD description (English source)
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.