Advisory

GHSA-8rwr-f68v-cvw6

Also known as: CVE-2026-46553

Summary

NocoDB: Attachment Size Limit Bypass via Upload-by-URL

Details

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.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-05-21 20:38 UTC
Modified
2026-07-20 21:30 UTC

Affected packages and fixes

nocodb

npm · All systems

Affected

  • introduced 0, last affected 0.301.3 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences