CVE-2026-53927

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
5.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.1Exploit: None knownExposed services: Not assessed

A fixed version is listed under Patch Availability — apply it.

NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, the spreadsheet-fetch endpoint (axiosRequestMake) accepted URLs whose path contained a permitted extension anywhere in the string, and applied a hand-rolled regex blocklist that omitted 127.0.0.0/8 and 169.254.0.0/16, allowing the cloud-metadata endpoint to be reached with a crafted URL This vulnerability is fixed in 2026.05.1.

CVSS v3
5.1
EG Score
5.1MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100

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%
EPSS PROB
0.4%
EPSS %ILE
30th
KEV
Not listed

Published

June 17, 2026

Last Modified

June 25, 2026

Advisory Details (1)

Auto-updated Jun 27, 2026
Fixed version listed under Patch Availability. Sources: github.
githubMentions a patch (unverified)

Server-Side Request Forgery via Spreadsheet Fetch URL · Advisory · nocodb/nocodb · GitHub

https://github.com/nocodb/nocodb/security/advisories/GHSA-gprh-27j3-g5h4

Vendor Advisories for CVE-2026-53927(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 / EcosystemFix (by version range) / PatchReleasedSource
npmnocodb—ghsa

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 rangeFix by version rangeDependents
nocodb—
  • every version through 0.301.3: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 26× 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 188 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-53927?
CVE-2026-53927 is a medium vulnerability published on June 17, 2026. NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, the spreadsheet-fetch endpoint (axiosRequestMake) accepted URLs whose path contained a permitted extension anywhere in the string, and applied a hand-rolled regex blocklist that omitted 127.0.0.0/8 and 169.254.0.0/16,…
When was CVE-2026-53927 disclosed?
CVE-2026-53927 was first published 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-53927 actively exploited?
CVE-2026-53927 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53927?
CVE-2026-53927 has a CVSS base score of 5.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53927?
A fixed version for CVE-2026-53927 is listed under Patch Availability on this page: update to the version listed for your package. The vendor advisories EchelonGraph has for CVE-2026-53927 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-53927?

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

Book a Demo →Browse All CVEs