Am I affected by n8n: Authenticated Users Can Exhaust Temporary Disk Storage via Data-Table File Uploads? What should I do?
An authenticated user can repeatedly upload files to the data-table upload endpoint, bypassing the per-request quota check, which does not account for files already written to the shared temporary directory.
Affected: npm/n8n >= 2.0.0, < 2.28.0 and npm/n8n < 1.123.58. Fixed in: 2.28.0 and 1.123.58. What should you check, and what should you do about it?
Full incident page with sources: https://agentarmorhq.com/incidents/2026/07/cve-2026-58661-n8n (opens external site)
1 answer
Am I affected? Affected: npm/n8n >= 2.0.0, < 2.28.0 and npm/n8n < 1.123.58. Fixed in: 2.28.0 and 1.123.58.
- Check your version: run
npm ls n8n. Versions >= 2.0.0, < 2.28.0 of n8n are affected.
What to do now
- Upgrade to the fixed version: run
npm install n8n@2.28.0(first patched version 2.28.0). - Restrict n8n instance access to fully trusted users only.
- Set
uploadMaxFileSizeto a low value to limit individual upload size. - Monitor and alert on disk usage in the n8n temporary upload directory.
General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.
Sources
- GitHub Advisory Database: https://github.com/advisories/GHSA-w867-jm58-p9pv (opens external site)
Full incident page: https://agentarmorhq.com/incidents/2026/07/cve-2026-58661-n8n (opens external site)
Did this work for you?- Check your version: run