CVE-2026-59206: n8n · Prototype Pollution
Affects n8nSource CVE Database V5
Not known to be exploited · CVSS 7.1 High · fixed in 2.28.1 : patch n8n soon.
Data as of 21 Nov 2026, 17:35 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.28.1, 2.27.4, 1.123.61
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 21 Nov 2026.
What to do
Upgrade n8n and n8n-io/n8n to 2.28.1, 2.27.4 or 1.123.61.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| n8n-ion8n | Affected
| Fixed in
|
| n8n-ion8n | Affected
| Fixed in
|
| n8n-ion8n | Affected
| Fixed in
|
npmn8n-io/n8npkg:npm/n8n-io/n8nOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in n8n versions 1.123.61, 2.27.4, and 2.28.1. Users should upgrade to these or later versions to remediate the issue. No vendor advisory content contradicts this; therefore, upgrading is the recommended mitigation.
Description
n8n, an open source workflow automation platform, contains a prototype pollution vulnerability (CWE-1321) in versions prior to 1.123.61, 2.27.4, and 2.28.1. An authenticated user with the default workflow:create permission can craft workflows that pollute Object.prototype via the workflow API. This pollution can cause unauthenticated requests to be treated as privileged users, exposing user and project listing endpoints. The issue is fixed in versions 1.123.61, 2.27.4, and 2.28.1.