CVE-2026-103251: n8n · Missing Authorization
Affects n8nSource CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in 2.40.1 : patch n8n soon.
Data as of 14 Nov 2026, 20:43 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.40.1, 2.39.6, 1.123.80
CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Oct 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 24 Oct 2026.
What to do
Upgrade n8n and n8n-io/n8n to 2.40.1, 2.39.6 or 1.123.80.
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
The vulnerability affects specific versions of n8n as stated. Users should upgrade to versions 1.123.80 or later, 2.39.6 or later, and 2.40.1 or later where this issue is fixed. Since this is not a cloud service, remediation requires applying these version upgrades. Patch status is confirmed by the version ranges affected and fixed versions implied by the version intervals. No vendor advisory content was provided to contradict this.
Description
CVE-2026-103251 is a high-severity vulnerability in n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1. It involves a validation bypass in the community package installation handler for queue mode deployments. Attackers with Redis write access can bypass multiple security checks to install arbitrary npm packages across all cluster instances without authentication.