n8n · Duplicate Advisory: Authenticated Users Can Exhaust Temporary Disk Storage via Data-Table File Uploads
Affects n8nSource GCVE Database
Not known to be exploited · CVSS 4.3 Medium : upgrade to 2.28.0 or 1.123.58 when convenient.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.28.0, 1.123.58
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 10 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade n8n-io/n8n to 2.28.0 or 1.123.58.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubn8n-io/n8npkg:github/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
Upgrade n8n to version 2.28.0 or later, or to version 1.123.58 or later on the 1.x branch, where this issue is fixed. Since this is a software vulnerability and not a cloud service, remediation requires applying the official patch by updating the affected software versions.
Description
CVE-2026-58661 affects n8n versions before 2.28.0 and before 1.123.58 on the 1.x branch. Authenticated users can exploit a flaw in the data-table file upload endpoint to exhaust disk space by repeatedly uploading files. The vulnerability exists because the quota check does not account for files already stored in the shared temporary directory, allowing accumulation until periodic cleanup. This can cause the host system's disk space to be fully consumed.