CVE-2026-49465: n8n: Git Node Clone and Push Operations Bypass File Sandbox
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 N8NRESTRICTFILEACCESSTO 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 NODESEXCLUDE environment variable.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Other sources
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 N8NRESTRICTFILEACCESSTO 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.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.21.8 - Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.22.4 - Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 1.123.48 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 1.123.48 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.21.8 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.22.4 - Configuration
Temporarily mitigate by disabling the Git node: add `n8n-nodes-base.git` to the `NODES_EXCLUDE` environment variable.
n8n NODES_EXCLUDE = n8n-nodes-base.git - Configuration
Temporarily mitigate by limiting workflow creation and editing permissions to fully trusted users only.
n8n workflow creation/modification permissions = fully trusted users only
Event History
Frequently Asked Questions
What is the severity of CVE-2026-49465?
The severity of CVE-2026-49465 is classified as high with a score of 7.7.
How do I fix CVE-2026-49465?
To fix CVE-2026-49465, ensure that the `N8N_RESTRICT_FILE_ACCESS_TO` is correctly configured to prevent unauthorized file access.
What type of vulnerability is CVE-2026-49465?
CVE-2026-49465 is a path traversal vulnerability that affects the n8n workflow automation tool.
Who is affected by CVE-2026-49465?
Authenticated users with permission to create or modify workflows in n8n are affected by CVE-2026-49465.
What could be the impact of exploiting CVE-2026-49465?
Exploiting CVE-2026-49465 could allow an attacker to bypass file access restrictions and access sensitive files on the server.