Skip to main content
VulnerabilityPublished

CVE-2026-49465: n8n · Path Traversal

Affects n8nSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.0 Medium · fixed in 2.22.4 : update n8n when convenient.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.22.4, 2.21.8, 1.123.48
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade n8n and n8n-io/n8n to 2.22.4, 2.21.8 or 1.123.48.

Affected software

ProductAffectedFixed in
n8n-ion8nAffected
  • >=2.22.0 <2.22.4
Fixed in
  • 2.22.4
n8n-ion8nAffected
  • >=2.0.0-rc.0 <2.21.8
Fixed in
  • 2.21.8
n8n-ion8nAffected
  • <1.123.48
Fixed in
  • 1.123.48
npmn8n-io/n8npkg:npm/n8n-io/n8nOther threatsAffected
  • <1.123.48
  • <2.21.8
  • <2.22.4
Fixed in
  • 1.123.48
  • 2.21.8
  • 2.22.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade n8n to version 1.123.48, 2.21.8, or 2.22.4 or later, where this vulnerability is fixed. No other mitigation or workaround is indicated. Patch status is confirmed by the vendor advisory specifying fixed versions.

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.

References

Community reviews

Loading reviews…