NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, the spreadsheet-import endpoint axiosRequestMake could be used as a generic HTTP proxy. Before the fix it was reachable unauthenticated, and its URL-extension allowlist was a regex tested against the full URL string, so URLs whose query string ended in .csv satisfies the gate even though the underlying request is for another file. This vulnerability is fixed in 2026.05.1.
CVE-2026-53931
This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 67% 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.9
- EG Score
- 6.9(medium)
- EG Risk
- 36(Track)EG Risk 36/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 computedSeverity69% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 33%
- KEV
- Not listed
Published
June 17, 2026
Last Modified
June 25, 2026
Advisory Details (1)
Auto-updated Jun 24, 2026Server-Side Request Forgery via Spreadsheet Import Endpoint · Advisory · nocodb/nocodb · GitHub
https://github.com/nocodb/nocodb/security/advisories/GHSA-hmcr-rmjq-47qrVendor Advisories for CVE-2026-53931(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 / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| npm | nocodb | — | 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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nocodb | — | — | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 76× 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 151 total refreshes for this CVE.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 06:54 UTCEG score recompute
- 2026-08-25 06:54 UTCGHSA enrichment
- 2026-08-24 06:59 UTCGHSA enrichment
- 2026-08-23 04:28 UTCEG score recompute
- 2026-08-23 04:28 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 07:54 UTCEG score recompute
- 2026-08-21 07:54 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 08:16 UTCEG score recompute
- 2026-08-20 08:16 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 08:12 UTCEG score recompute
- 2026-08-19 08:12 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 23:28 UTCEG score recompute
- 2026-08-16 23:28 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 23:50 UTCEG score recompute
- 2026-08-15 23:50 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-15 00:12 UTCGHSA enrichment
- 2026-08-14 00:34 UTCEG score recompute
- 2026-08-14 00:34 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 00:56 UTCEG score recompute
- 2026-08-13 00:56 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 01:19 UTCEG score recompute
- 2026-08-12 01:19 UTCGHSA enrichment
- 2026-08-11 01:41 UTCEG score recompute
- 2026-08-11 01:41 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 02:04 UTCEG score recompute
- 2026-08-10 02:04 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 02:26 UTCEG score recompute
- 2026-08-09 02:26 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 02:49 UTCEG score recompute
- 2026-08-08 02:49 UTCGHSA enrichment
- 2026-08-07 03:11 UTCEG score recompute
- 2026-08-07 03:11 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 03:33 UTCEG score recompute
- 2026-08-06 03:33 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 03:55 UTCEG score recompute
- 2026-08-05 03:55 UTCGHSA enrichment
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 04:18 UTCEG score recompute
- 2026-08-04 04:18 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 04:39 UTCGHSA enrichment
- 2026-08-02 05:01 UTCEG score recompute
- 2026-08-02 05:01 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 05:23 UTCEG score recompute
- 2026-08-01 05:23 UTCGHSA enrichment
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 03:57 UTCEG score recompute
- 2026-07-31 03:57 UTCGHSA enrichment
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 03:43 UTCEG score recompute
- 2026-07-30 03:43 UTCGHSA enrichment
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 02:17 UTCEG score recompute
- 2026-07-29 02:17 UTCGHSA enrichment
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-28 01:16 UTCEG score recompute
- 2026-07-28 01:16 UTCGHSA enrichment
- 2026-07-26 19:10 UTCEG score recompute
- 2026-07-26 19:10 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:19 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 12:55 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 13:17 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 11:20 UTCGHSA enrichment
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 11:34 UTCGHSA enrichment
- 2026-07-13 06:13 UTCEPSS rescore
Related CVEs(same product + same CWE)
Same product
10 shownnpm:nocodb
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p92CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
- CVE-2018-0403EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-53931?
When was CVE-2026-53931 disclosed?
Is CVE-2026-53931 actively exploited?
What is the CVSS score of CVE-2026-53931?
How do I remediate CVE-2026-53931?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53931
Is Your Infrastructure Affected by CVE-2026-53931?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.