Quick answers
- Is CVE-2026-53930 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53930 being exploited in the wild.
- How severe is CVE-2026-53930?
- 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-53930?
- A patch was published on 2026-05-01: Fixed in version 2026.05.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53930 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-53930?
- 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 Server-Side Request Forgery (SSRF) vulnerability exists in NocoDB's base-migration endpoint due to insufficient validation of the 'migrationUrl' parameter. Prior to version 2026.05.1, the migration worker dereferenced caller-supplied URLs without enforcing protocol restrictions or destination filtering. An attacker with the 'workspace owner' role could exploit this to abuse URI schemes (such as file: or ftp:) to read local files or probe internal HTTP destinations. The fix implemented in 2026.05.1 introduces strict protocol validation (limiting requests to http: and https:) and utilizes request-filtering-agent to block access to private IP ranges (RFC 1918), loopback, and link-local addresses.
Affected products
- NocoDB NocoDB < 2026.05.1
Identifiers
- CVE-2026-53930
- GHSA-h6vv-pcq8-7xm4
Timeline
- 2026-06-13: advisory: GitHub Security Advisory published
- 2026-06-23: disclosed: CVE published to NVD
- 2026-05-01: patched: Fixed in version 2026.05.1