dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2026-58661

MEDIUM · 5.3 CVSS v4.0 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
n8n before 2.28.0 (and before 1.123.58 on the 1.x branch) contains a disk space exhaustion vulnerability in the data-table file upload endpoint. The per-request quota check does not account for files already written to the shared temporary directory, allowing an authenticated user to repeatedly upload files that accumulate on disk until the periodic cleanup runs, potentially exhausting available disk space on the host.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

n8n before 2.28.0 (and 1.123.58) has a disk space exhaustion vulnerability in the data-table file upload endpoint. The per-request quota check does not track cumulative files already written to the shared temporary directory, allowing authenticated users to repeatedly upload files that accumulate on disk until the periodic cleanup runs, potentially exhausting available disk space.

MitigationUpgrade to n8n version 2.28.0 or later (or 1.123.58+ on the 1.x branch) to receive the patch that fixes the quota accounting logic.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed n8n version
    Run the command `n8n --version` or check the version via the UI at Settings > About. If running as a Docker container, use `docker exec <container> n8n --version`.
    Affected if The installed version is before 2.28.0 on the 2.x branch or before 1.123.58 on the 1.x branch.
  2. Confirm the data-table feature is enabled
    Check if n8n has the data-table node or any workflow that utilizes the data-table file upload functionality. Inspect workflow configurations for nodes named 'data-table' or look for file upload operations within data-table contexts.
    Affected if The data-table node or its file upload capability is actively used in any workflow.
  3. Inspect the shared temporary directory for file accumulation
    Locate the n8n temporary directory (typically under the n8n user data folder, often in a temp or tmp subdirectory). Use `find /path/to/n8n/temp -type f -mtime -1` to list recently created files, and run `du -sh /path/to/n8n/temp` to check the total size of stored temporary files.
    Affected if Temporary files from data-table uploads are accumulating and the directory size is growing beyond expected per-request quotas.
  4. Monitor disk space usage on the n8n host
    Run `df -h` on the n8n server to check available disk space. Repeatedly check this while monitoring for any rapid decrease in available space that correlates with file upload activity.
    Affected if Disk space is decreasing over time without other explanation, indicating potential file accumulation from repeated uploads.

You are affected if your n8n version is below 2.28.0 (or below 1.123.58 on the 1.x branch) AND the data-table file upload endpoint is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to n8n version 2.28.0 or later (or 1.123.58+ on the 1.x branch) to receive the patch that fixes the quota accounting logic.

Recommended fix High confidence

n8n 2.28.0 (2.x branch) or n8n 1.123.58 (1.x branch)

  1. Identify currently running n8n version (1.x or 2.x branch)
  2. If running 1.x branch, upgrade to n8n version 1.123.58 or later
  3. If running 2.x branch, upgrade to n8n version 2.28.0 or later
  4. After upgrade, verify the data-table file upload endpoint properly enforces quota including temporary files

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58661 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-58661 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data