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.
CVE-2026-46551
Score 6.5 from GitHub Security Advisory published 2026-05-21. a secondary CVSS source baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- —
- EPSS
- 14.5%
- KEV
- Not listed
Published
May 21, 2026
Last Modified
June 25, 2026
Advisory Details (1)
Auto-updated Jun 24, 2026Missing File Size Limit on Upload-by-URL · Advisory · nocodb/nocodb · GitHub
https://github.com/nocodb/nocodb/security/advisories/GHSA-99vc-2jx2-688pVendor Advisories for CVE-2026-46551(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| npm | nocodb | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nocodb | — | — | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 34× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 21:59 UTCOSV refresh
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 19:56 UTCGHSA enrichment
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
Show 31 moreShow fewer
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 20:29 UTCGHSA enrichment
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 19:20 UTCGHSA enrichment
- 2026-06-25 14:14 UTCGHSA enrichment
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-18 02:35 UTCGHSA enrichment
- 2026-06-17 01:26 UTCGHSA enrichment
- 2026-06-16 00:19 UTCGHSA enrichment
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-14 23:11 UTCGHSA enrichment
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-13 22:03 UTCGHSA enrichment
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 15:05 UTCGHSA enrichment
- 2026-06-11 13:56 UTCGHSA enrichment
- 2026-06-10 12:48 UTCGHSA enrichment
- 2026-06-09 11:40 UTCGHSA enrichment
- 2026-06-08 10:32 UTCGHSA enrichment
- 2026-06-07 09:24 UTCGHSA enrichment
- 2026-06-06 08:17 UTCGHSA enrichment
- 2026-06-05 07:10 UTCGHSA enrichment
- 2026-06-04 06:02 UTCGHSA enrichment
- 2026-06-03 04:54 UTCGHSA enrichment
- 2026-06-02 03:46 UTCGHSA enrichment
- 2026-06-01 02:38 UTCGHSA enrichment
- 2026-05-24 06:10 UTCEG score recompute
- 2026-05-24 06:10 UTCGHSA enrichment
Related CVEs(same product + same CWE)
Same product
10 shownnpm:nocodb
Same CWE
10 shownCWE-770
Frequently asked(5)
What is CVE-2026-46551?
When was CVE-2026-46551 disclosed?
Is CVE-2026-46551 actively exploited?
What is the CVSS score of CVE-2026-46551?
How do I remediate CVE-2026-46551?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46551
Is Your Infrastructure Affected by CVE-2026-46551?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.