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.3%, top 79% 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 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.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 27, 2026
Patch available. Sources: github.
github Patch Available

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 / EcosystemFixed in / 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 rangeFixed inDependents
nocodb———

Weakness Classification(1)

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

Data Freshness Timeline

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

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

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 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-53927 actively exploited?
CVE-2026-53927 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-53927?
CVE-2026-53927 has a CVSS v3 base score of 5.1 (NVD).
How do I remediate CVE-2026-53927?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53927, 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-53927

Explore →

Is Your Infrastructure Affected by CVE-2026-53927?

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

Start Free Scan →Browse All CVEs