NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-46553: NocoDB: Attachment Size Limit Bypass via Upload-by-URL

lowCVSS 4.0 2.1GHSA-8rwr-f68v-cvw6

Summary The upload-by-URL path did not enforce NCATTACHMENTFIELDSIZE against either the remote file's advertised Content-Length or the decoded length of a data: URI, allowing an authenticated user to bypass the configured per-file size limit. Details The attachments service now checks NCATTACHMENTFIELDSIZE against both the HEAD response's content-length and the decoded length of a data: URI body before fetching.

Published May 21, 2026 · Updated Jul 20, 2026

Affected packages

nocodb

Ecosystem
npm
Affected
<= 0.301.3
Fixed in
No patched version yet
Check
npm ls nocodb

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Summary

The upload-by-URL path did not enforce NC_ATTACHMENT_FIELD_SIZE against either the remote file's advertised Content-Length or the decoded length of a data: URI, allowing an authenticated user to bypass the configured per-file size limit.

Details

The attachments service now checks NC_ATTACHMENT_FIELD_SIZE against both the HEAD response's content-length and the decoded length of a data: URI body before fetching. The local storage plugin additionally sets maxContentLength on the axios download so a malicious server cannot stream past the limit.

Impact

Authenticated users with upload permission could attach files larger than the operator-configured limit, defeating storage and bandwidth caps.

Credit

This issue was reported by @bugbunny-research.

Credited to bugbunny-research.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries