n8n-io · n8n
The n8n workflow automation platform, in versions from 1.65.0 before 1.121.0, contains a flaw in how form-based workflows handle incoming webhook requests. An unauthenticated remote attacker can exploit a vulnerable workflow over the network, with no user interaction required, to read files on the underlying server, potentially exposing sensitive stored information and enabling further compromise depending on deployment configuration and how the workflow is used.
n8n is an open source workflow automation platform. Versions starting with 1.65.0 and below 1.121.0 enable an attacker to access files on the underlying server through execution of certain form-based workflows. A vulnerable workflow could grant access to an unauthenticated remote attacker, resulting in exposure of sensitive information stored on the system and may enable further compromise depending on deployment configuration and workflow usage. This issue is fixed in version 1.121.0.
First seen exploited 2 days after disclosure. Public exploit code (PoC-in-GitHub) was available the same day.
7 fixes in n8n over 9 weeks. The latest fix listed for n8n is 1.121.3.
No ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.
1 package in 1 ecosystem. Main package: n8n.
Upgrade to 1.121.1 or later
Fixes this CVE and 1 other known vulnerability in this package (CVE-2025-68613).
npm install n8n@1.121.1First fixed in 1.121.0 for CVE-2026-21858.
| If you run | Upgrade to |
|---|---|
| 1.65.0 up to 1.121.0 | 1.121.1first fix for this CVE: 1.121.0 |
“Up to” means the second version is the fix and is not affected.
Pulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.