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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.1 · 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 · score source

EPSS

• CVE-2026-46553: 0.41% estimated exploitation activity in the next 30 days; percentile 34.88 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. 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.

Published by the source

21 May 2026, 20:38 UTC

Last modified by the source

20 Jul 2026, 21:30 UTC

Source last checked

26 Oct 2026, 12:57 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-8rwr-f68v-cvw6

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-8rwr-f68v-cvw6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-46553

Advisory: NocoDB: Attachment Size Limit Bypass via Upload-by-URL
IDs: CVE-2026-46553, GHSA-8rwr-f68v-cvw6
Record: https://patchnext.com/advisories/cve-2026-46553 (revision 3, source checked 26 Oct 2026, 12:57 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nocodb: affected <= 0.301.3

## Suggested inspection (read-only)
- `npm ls nocodb --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nocodb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-8rwr-f68v-cvw6 (OSV record GHSA-8rwr-f68v-cvw6 lists affected ranges: npm nocodb >=0 <=0.301.3)
- Verified: https://github.com/advisories/GHSA-8rwr-f68v-cvw6 (GitHub-reviewed advisory GHSA-8rwr-f68v-cvw6 lists affected ranges: npm nocodb >=0 <=0.301.3)

Commands are suggestions: review each one before running it.