Quick answers
- Is CVE-2026-46553 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46553 being exploited in the wild.
- How severe is CVE-2026-46553?
- Medium severity, with a CVSS score of 4, published 23 June 2026.
- Which products and versions are affected?
- nocodb (npm) <= 0.301.3, SEMVER:introduced=0,last_affected=0.301.3.
- Is there a fix for CVE-2026-46553?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-46553 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-46553?
- Check whether you run nocodb (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A resource exhaustion vulnerability (CWE-770) exists in NocoDB's attachment service. Prior to version 2026.04.1, the 'upload-by-URL' path failed to validate the NC_ATTACHMENT_FIELD_SIZE configuration against the Content-Length header of remote files or the decoded length of data URIs. An authenticated attacker with upload permissions could exploit this to bypass per-file size limits. The fix introduces checks against HEAD response headers and data URI lengths, and implements maxContentLength constraints on the underlying axios download requests to prevent streaming beyond the limit.
Affected products
- NocoDB NocoDB < 2026.04.1
Identifiers
- CVE-2026-46553
- GHSA-8rwr-f68v-cvw6
Timeline
- 2026-05-19: advisory: GitHub Security Advisory published
- 2026-06-23: disclosed: CVE published to NVD