CVE-2026-46551: NocoDB Remote Code Execution Vulnerability

MODERATE
Advisory Identifier: GHSA-99vc-2jx2-688p
Share
CVSS 6.5
CWE-770
Published
Advisory Summary

CVE-2026-46551 is a MODERATE (CVSS 6.5) remote code execution vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting NocoDB libraries in the npm ecosystem. The issue involves missing file size enforcement in upload-by-url allows denial of service via disk exhaustion. Remediation is available in the latest vendor maintenance releases.

CVE-2026-46551 at a Glance

CVE Identifier CVE-2026-46551
GHSA Identifier GHSA-99vc-2jx2-688p
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-770: Allocation of Resources Without Limits or Throttling
Affected Product NocoDB
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-46551

To remediate this vulnerability, upgrade all affected NocoDB dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

nocodb fixed: Latest secure release 
npm install nocodb@Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls nocodb

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-46551, inspect your project dependencies using npm:

npm ls nocodb

Analyze the terminal output to locate any version of NocoDB in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The npm ls nocodb command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In NocoDB, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary 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. ### Details 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`. The v3 service (`v3/data-attachment-v3.service.ts`) already enforced the limit, but the v1/v2 endpoints (`POST /api/v1/db/storage/upload-by-url`, `POST /api/v2/storage/upload-by-url`) did not. This is distinct from GHSA-xr7v-j379-34v9 (blind SSRF via HEAD) — same code area, different class. ### Impact - Authenticated DoS via disk exhaustion. Editor role suffices. - Cascading failures once disk fills: blocked DB writes, log rotation, application crash. ### Credit This issue was reported by [@ik0z](https://github.com/ik0z).

CVE-2026-46551 Affected NocoDB Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
nocodb
npm/nocodb
npm
≤ 0.301.3

References

GitHub Advisory / Wiki ADVISORY
https://github.com/nocodb/nocodb/security/advisories/GHSA-99vc-2jx2-688p
NVD — CVE-2026-46551 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-46551
NocoDB Source Repository REPOSITORY
https://github.com/nocodb/nocodb

Frequently Asked Questions

What is CVE-2026-46551?
CVE-2026-46551 is a security vulnerability in NocoDB involving Missing File Size Enforcement in Upload-by-URL Allows Denial of Service via Disk Exhaustion under CWE-770: Allocation of Resources Without Limits or Throttling.
Which NocoDB versions are affected?
Affected versions include releases prior to current release patches across affected packages: nocodb.
What version fixes CVE-2026-46551?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is nocodb affected?
Yes, nocodb is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-46551?
CVE-2026-46551 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-46551?
CVE-2026-46551 is classified under CWE-770: Allocation of Resources Without Limits or Throttling (The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.).
How can I check npm dependencies for CVE-2026-46551?
Run the dependency tree command: 'npm ls nocodb'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-99vc-2jx2-688p",
  "modified" : "2026-07-20T21:16:33Z",
  "published" : "2026-05-21T20:35:41Z",
  "aliases" : [ "CVE-2026-46551" ],
  "summary" : "NocoDB: Missing File Size Enforcement in Upload-by-URL Allows Denial of Service via Disk Exhaustion",
  "details" : "### Summary\n\nThe `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.\n\n### Details\n\nIn `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`. The v3 service (`v3/data-attachment-v3.service.ts`) already enforced the limit, but the v1/v2 endpoints (`POST /api/v1/db/storage/upload-by-url`, `POST /api/v2/storage/upload-by-url`) did not.\n\nThis is distinct from GHSA-xr7v-j379-34v9 (blind SSRF via HEAD) — same code area, different class.\n\n### Impact\n\n- Authenticated DoS via disk exhaustion. Editor role suffices.\n- Cascading failures once disk fills: blocked DB writes, log rotation, application crash.\n\n### Credit\n\nThis issue was reported by [@ik0z](https://github.com/ik0z).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "nocodb"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "0.301.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/nocodb/nocodb/security/advisories/GHSA-99vc-2jx2-688p"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-46551"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/nocodb/nocodb"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-770" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-21T20:35:41Z",
    "nvd_published_at" : "2026-06-23T21:16:58Z"
  }
}