dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2026-46551

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
NocoDB is software for building databases as spreadsheets. Prior to 2026.04.4, the uploadViaURL path in the v1/v2 attachment API did not enforce NC_ATTACHMENT_FIELD_SIZE against the remote content-length or against the response stream. An authenticated user (Editor+) could direct the server to download arbitrarily large files, exhausting disk space and causing denial of service. In packages/nocodb/src/services/attachments.service.ts, the HEAD probe read content-length but never compared it to NC_ATTACHMENT_FIELD_SIZE; the subsequent storageAdapter.fileCreateByUrl() performed the download without maxContentLength. This vulnerability is fixed in 2026.04.4.

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

In NocoDB prior to 2026.04.4, the uploadViaURL endpoint in the v1/v2 attachment API fails to validate the remote file size against NC_ATTACHMENT_FIELD_SIZE before downloading. An authenticated Editor+ user can supply a URL to an arbitrarily large file, causing the server to download the full content and exhaust disk space, resulting in denial of service.

MitigationUpgrade to NocoDB version 2026.04.4 or later, which implements content-length validation in the HEAD probe and enforces maxContentLength during file download.

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
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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. Check NocoDB version
    Access the NocoDB administration panel or check the running container/package version to determine the installed version. Compare it against the affected range (any version prior to 2026.04.4).
    Affected if The installed version is earlier than 2026.04.4 (e.g., 2026.03.0, 2025.x.x, etc.)
  2. Verify uploadViaURL endpoint exists
    Confirm that the v1/v2 attachment API with the uploadViaURL endpoint is exposed in the NocoDB instance. This is typically accessible at /api/v1/db/data/attachment/uploadViaURL or similar paths under the API base.
    Affected if The endpoint is present and reachable without additional security restrictions
  3. Check user role permissions
    Review the role-based access control settings to determine if Editor-level or higher users exist in the system. The vulnerability requires an authenticated Editor+ user.
    Affected if Editor, Owner, or Super Admin roles are enabled and users with these roles can access the attachment API
  4. Inspect NC_ATTACHMENT_FIELD_SIZE configuration
    Examine the NocoDB environment variables or configuration files for the NC_ATTACHMENT_FIELD_SIZE setting. This parameter should limit attachment sizes but is not being checked by the vulnerable endpoint.
    Affected if NC_ATTACHMENT_FIELD_SIZE is set to a permissive value or is not enforced on the uploadViaURL endpoint

A user is affected if NocoDB version is earlier than 2026.04.4, the uploadViaURL endpoint is accessible, and Editor+ users can access the attachment API without proper file size validation.

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 NocoDB version 2026.04.4 or later, which implements content-length validation in the HEAD probe and enforces maxContentLength during file download.

Recommended fix High confidence

2026.04.4

  1. Backup the NocoDB database and configuration files before proceeding with the upgrade
  2. Stop the NocoDB service to prevent data corruption during upgrade
  3. Upgrade NocoDB to version 2026.04.4 (use the appropriate method for your installation: Docker image tag, npm install, or binary release)
  4. Verify the upgrade was successful by checking the installed version
  5. Start the NocoDB service

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46551 — 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-46551 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