CVE-2026-53930

MEDIUMPre-NVD 5.15.1
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
5.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, the base-migration endpoint accepted a caller-supplied URL that the migration worker dereferenced without enforcing protocol or destination, allowing scheme abuse (file:, ftp:, etc.) and probing of internal HTTP destinations. This vulnerability is fixed in 2026.05.1.

CVSS v3
5.1
EG Score
5.1(medium)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity51% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

June 17, 2026

Last Modified

June 25, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
Patch available. Sources: github.
github Patch Available

Server-Side Request Forgery via Base Migration URL · Advisory · nocodb/nocodb · GitHub

https://github.com/nocodb/nocodb/security/advisories/GHSA-h6vv-pcq8-7xm4

Vendor Advisories for CVE-2026-53930(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
npmnocodbghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
nocodb

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 69× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 146 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-25 07:12 UTCEG score recompute
  3. 2026-08-25 07:12 UTCGHSA enrichment
  4. 2026-08-24 06:59 UTCGHSA enrichment
  5. 2026-08-23 04:28 UTCEG score recompute
  6. 2026-08-23 04:28 UTCGHSA enrichment
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 08:38 UTCEG score recompute
  10. 2026-08-21 08:38 UTCGHSA enrichment
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-20 08:25 UTCEG score recompute
  13. 2026-08-20 08:25 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 08:12 UTCEG score recompute
  16. 2026-08-19 08:12 UTCGHSA enrichment
  17. 2026-08-18 13:48 UTCEPSS rescore
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-16 22:08 UTCEG score recompute
  20. 2026-08-16 22:08 UTCGHSA enrichment
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 02:14 UTCEPSS rescore
  23. 2026-08-15 21:55 UTCEG score recompute
  24. 2026-08-15 21:55 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 75 more
  1. 2026-08-14 20:19 UTCEG score recompute
  2. 2026-08-14 20:19 UTCGHSA enrichment
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 20:06 UTCGHSA enrichment
  5. 2026-08-12 19:52 UTCEG score recompute
  6. 2026-08-12 19:52 UTCGHSA enrichment
  7. 2026-08-12 13:51 UTCEPSS rescore
  8. 2026-08-11 19:39 UTCEG score recompute
  9. 2026-08-11 19:39 UTCGHSA enrichment
  10. 2026-08-11 00:00 UTCEPSS rescore
  11. 2026-08-10 19:26 UTCGHSA enrichment
  12. 2026-08-09 19:13 UTCEG score recompute
  13. 2026-08-09 19:13 UTCGHSA enrichment
  14. 2026-08-09 13:46 UTCEPSS rescore
  15. 2026-08-08 19:01 UTCGHSA enrichment
  16. 2026-08-07 18:48 UTCEG score recompute
  17. 2026-08-07 18:48 UTCGHSA enrichment
  18. 2026-08-06 18:35 UTCEG score recompute
  19. 2026-08-06 18:35 UTCGHSA enrichment
  20. 2026-08-06 13:47 UTCEPSS rescore
  21. 2026-08-05 19:17 UTCEPSS rescore
  22. 2026-08-05 18:22 UTCGHSA enrichment
  23. 2026-08-04 15:27 UTCEG score recompute
  24. 2026-08-04 15:27 UTCGHSA enrichment
  25. 2026-08-04 15:10 UTCEPSS rescore
  26. 2026-08-04 10:39 UTCEPSS rescore
  27. 2026-08-03 08:47 UTCGHSA enrichment
  28. 2026-08-02 05:36 UTCEG score recompute
  29. 2026-08-02 05:36 UTCGHSA enrichment
  30. 2026-08-02 02:27 UTCEPSS rescore
  31. 2026-08-01 05:23 UTCEG score recompute
  32. 2026-08-01 05:23 UTCGHSA enrichment
  33. 2026-08-01 04:16 UTCEPSS rescore
  34. 2026-07-31 03:57 UTCEG score recompute
  35. 2026-07-31 03:57 UTCGHSA enrichment
  36. 2026-07-30 16:28 UTCEPSS rescore
  37. 2026-07-30 03:43 UTCEG score recompute
  38. 2026-07-30 03:43 UTCGHSA enrichment
  39. 2026-07-30 01:30 UTCEPSS rescore
  40. 2026-07-29 02:17 UTCEG score recompute
  41. 2026-07-29 02:17 UTCGHSA enrichment
  42. 2026-07-28 15:37 UTCEPSS rescore
  43. 2026-07-28 01:16 UTCEG score recompute
  44. 2026-07-28 01:16 UTCGHSA enrichment
  45. 2026-07-26 19:10 UTCEG score recompute
  46. 2026-07-26 19:10 UTCGHSA enrichment
  47. 2026-07-26 14:54 UTCEPSS rescore
  48. 2026-07-25 14:18 UTCEPSS rescore
  49. 2026-07-24 14:18 UTCEPSS rescore
  50. 2026-07-23 14:18 UTCEPSS rescore
  51. 2026-07-23 03:19 UTCEG score recompute
  52. 2026-07-22 14:08 UTCEPSS rescore
  53. 2026-07-20 17:08 UTCEPSS rescore
  54. 2026-07-19 14:31 UTCEPSS rescore
  55. 2026-07-19 14:31 UTCEPSS rescore
  56. 2026-07-19 02:29 UTCEPSS rescore
  57. 2026-07-18 10:04 UTCEPSS rescore
  58. 2026-07-16 22:54 UTCGHSA enrichment
  59. 2026-07-16 17:03 UTCEPSS rescore
  60. 2026-07-15 22:41 UTCGHSA enrichment
  61. 2026-07-15 16:57 UTCEPSS rescore
  62. 2026-07-15 16:57 UTCEPSS rescore
  63. 2026-07-15 02:00 UTCEPSS rescore
  64. 2026-07-15 02:00 UTCEPSS rescore
  65. 2026-07-14 22:28 UTCGHSA enrichment
  66. 2026-07-13 22:31 UTCEPSS rescore
  67. 2026-07-13 21:52 UTCGHSA enrichment
  68. 2026-07-13 06:13 UTCEPSS rescore
  69. 2026-07-13 06:13 UTCEPSS rescore
  70. 2026-07-12 21:39 UTCGHSA enrichment
  71. 2026-07-12 05:46 UTCEPSS rescore
  72. 2026-07-11 21:07 UTCGHSA enrichment
  73. 2026-07-11 08:27 UTCEPSS rescore
  74. 2026-07-11 08:27 UTCEPSS rescore
  75. 2026-07-10 20:54 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53930?
CVE-2026-53930 is a medium vulnerability published on June 17, 2026. NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, the base-migration endpoint accepted a caller-supplied URL that the migration worker dereferenced without enforcing protocol or destination, allowing scheme abuse (file:, ftp:, etc.) and probing of internal HTTP…
When was CVE-2026-53930 disclosed?
CVE-2026-53930 was first published in the National Vulnerability Database on June 17, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53930 actively exploited?
CVE-2026-53930 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.4% of all scored CVEs.
What is the CVSS score of CVE-2026-53930?
CVE-2026-53930 has a CVSS v3 base score of 5.1 (NVD).
How do I remediate CVE-2026-53930?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53930, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53930

Explore →

Is Your Infrastructure Affected by CVE-2026-53930?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.