GHSA-8rwr-f68v-cvw6

Suggest an improvement
Source
https://github.com/advisories/GHSA-8rwr-f68v-cvw6
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/05/GHSA-8rwr-f68v-cvw6/GHSA-8rwr-f68v-cvw6.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-8rwr-f68v-cvw6
Aliases
Published
2026-05-21T20:38:58Z
Modified
2026-07-20T21:30:36Z
Severity
  • 2.1 (Low) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P CVSS Calculator
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.

Database specific 
{
    "cwe_ids":  [
        "CWE-770"
    ],
    "github_reviewed":  true,
    "github_reviewed_at":  "2026-05-21T20:38:58Z",
    "nvd_published_at":  "2026-06-23T21:16:58Z",
    "severity":  "LOW"
}
References

Affected packages

npm / nocodb

Package

Name
nocodb
View open source insights on deps.dev
Purl
pkg:npm/nocodb

Affected ranges

Type
SEMVER
Events
Introduced
0 Unknown introduced version / All previous versions are affected
Last Affected
0.301.3

Database specific

source 
"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/05/GHSA-8rwr-f68v-cvw6/GHSA-8rwr-f68v-cvw6.json"