n8n is vulnerable to Remote Code Execution via Arbitrary File Write

published 2026-01-06 10 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-1037 , GHSA-v364-rw7m-3263

cvss: 10.0; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 5.4%; EPSS 5.4% chance of exploitation in 30 days, percentile 92%
public exploits: 0; none known, plus a Nuclei check

n8n is an open source workflow automation platform. In versions 0.121.2 and below, an authenticated attacker may be able to execute malicious code using the n8n service. This could result in full compromise and can impact both self-hosted and n8n Cloud instances. This issue is fixed in version 1.121.3. Administrators can reduce exposure by disabling the Git node and limiting access for untrusted users, but upgrading to the latest version is recommended.

Patch / fix

fixed in 2 links 1

npm n8n 1.121.3
n8n n8n 1.121.3

github.com/n8n-io/n8n@f4b009d commit

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 10 mo ago (2026-01-08)

Exploit prediction

5.45% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

Nuclei template n8n >= 0.123.0 and < 1.121.3 - Remote Code Execution nuclei detection template

CVSS scores

assigned by	version	score	vector
CNA	3.1	10.0	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
GitHub	3.1	9.9	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
npm	n8n	>=0.123.0, <1.121.3	1.121.3

Affected products

n8n-io n8n

Classification

Weakness

CWE-94 Improper Control of Generation of Code
CWE-434 Unrestricted Upload of File with Dangerous Type

References

github.com /n8n-io/n8n/commit/f4b009d00d1f4ba9359b8e8f1c071e3d910a55f6
patch
github.com /n8n-io/n8n/security/advisories/GHSA-v364-rw7m-3263
web, vendor-advisory
github.com /n8n-io/n8n
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary