CVE-2026-47385

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (38th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-38615 (ENISA EUVD) · GHSA-wvqj-9wv4-7ff5 (GitHub Security Advisories)Source: ENISA EUVD

5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, an authenticated user with base-create permission can attach a SQLite source pointing at an arbitrary file on the NocoDB host, including NocoDB's own internal databases. The SQLite client and the base/integration create services accepted a caller-supplied filename and passed it to fs.exists and fs.open('w') without restricting the location. A user could point a source at noco.db, at a tenant database under nc_minimal_dbs/, or at any writable path the NocoDB process can reach, and then read or overwrite its contents through the regular table APIs.This vulnerability is fixed in 2026.05.1.

CVSS
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
38th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 5, 2026

Last Modified

June 25, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Path Traversal via SQLite Source Filename · Advisory · nocodb/nocodb · GitHub

https://github.com/nocodb/nocodb/security/advisories/GHSA-wvqj-9wv4-7ff5

Vendor Advisories for CVE-2026-47385(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 @ 2026.05.1 (fixes <= 2026.05.0)—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 up to 2026.05.1: fixed in 2026.05.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 169 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 69 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-47385?
CVE-2026-47385 is a medium-severity vulnerability; its CVE record was published on June 5, 2026. NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, an authenticated user with base-create permission can attach a SQLite source pointing at an arbitrary file on the NocoDB host, including NocoDB's own internal databases. The SQLite client and the base/integration create…
When was the CVE record for CVE-2026-47385 published?
The CVE record for CVE-2026-47385 was published on June 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 25, 2026; the record at its source may have been updated since.
Is CVE-2026-47385 actively exploited?
CVE-2026-47385 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47385?
CVE-2026-47385 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47385?
A fix for CVE-2026-47385 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47385 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-47385

Explore →

Is Your Infrastructure Affected by CVE-2026-47385?

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