n8n: Git Node Clone and Push Operations Bypass File Sandbox
n8n
- Severity
- High, CVSS 7.7
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
- Record
- CVE-2026-49465
- Affects
- n8n
- Known exploited
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- Record first published by the source
- June 23, 2026
- Source last modified
- October 26, 2026
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.
Description quoted from the NVD record.
Who is affected
n8n is a tool for automating tasks by connecting apps and services into step-by-step workflows. This flaw affects versions before 1.123.48, 2.21.8 and 2.22.4, depending on which release line you use. A signed-in user who is allowed to create or change workflows could use the Git building block, through its Clone or Push actions, to get around the setting that limits which files n8n can reach. That person could then copy and read any Git code repository stored on the same computer that n8n can access, even though reading those files directly is blocked. This flaw is rated High.
What to do
- If someone in your organization installed n8n or looks after it, that person should check which version is running. Versions before
1.123.48,2.21.8and2.22.4have this flaw. - That person should update n8n to
1.123.48,2.21.8or2.22.4, picking the fixed version that matches the release line already in use. - If an IT provider or vendor runs n8n for your organization, send them this advisory and ask when the update will be done.
- For more details on the fixed releases, see the vendor advisory linked on this page.
Analysis written from the source record as of October 26, 2026 and reviewed before publishing.