CVE-2023-6023

HIGHNVD 7.58.6▲
EchelonGraph scoreMEDIUM confidence

Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2023-11-16. NVD baseline CVSS 7.5; sources differ by 1.1.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 3%CVSS: 7.5Exploit: NoneExposed: 0

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

An attacker can read any file on the filesystem on the server hosting ModelDB through an LFI in the artifact_path URL parameter.

CVSS v3
7.5
EG Score
8.6(medium)
EPSS
85.8%
KEV
Not listed

Published

November 16, 2023

Last Modified

June 17, 2026

References (2)

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 40× 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.

  1. 2026-07-11 08:26 UTCEPSS rescore
  2. 2026-07-09 19:08 UTCEPSS rescore
  3. 2026-07-08 15:13 UTCEPSS rescore
  4. 2026-07-07 13:45 UTCEPSS rescore
  5. 2026-07-07 13:44 UTCEPSS rescore
  6. 2026-07-06 16:26 UTCEPSS rescore
  7. 2026-07-06 16:26 UTCEPSS rescore
  8. 2026-07-06 02:22 UTCEPSS rescore
  9. 2026-07-06 02:22 UTCEPSS rescore
  10. 2026-07-05 02:29 UTCEPSS rescore
  11. 2026-07-04 06:29 UTCEPSS rescore
  12. 2026-07-01 15:05 UTCEPSS rescore
  13. 2026-06-30 23:21 UTCEPSS rescore
  14. 2026-06-30 23:21 UTCEPSS rescore
  15. 2026-06-29 14:05 UTCEPSS rescore
  16. 2026-06-28 14:06 UTCEPSS rescore
  17. 2026-06-28 14:06 UTCEPSS rescore
  18. 2026-06-28 04:55 UTCEPSS rescore
  19. 2026-06-27 03:07 UTCEPSS rescore
  20. 2026-06-25 13:48 UTCEPSS rescore
  21. 2026-06-25 13:48 UTCEPSS rescore
  22. 2026-06-24 14:04 UTCEPSS rescore
  23. 2026-06-24 14:04 UTCEPSS rescore
  24. 2026-06-23 21:31 UTCEPSS rescore
  25. 2026-06-23 21:31 UTCEPSS rescore
Show 40 more
  1. 2026-06-22 14:24 UTCEPSS rescore
  2. 2026-06-22 14:24 UTCEPSS rescore
  3. 2026-06-21 01:58 UTCEPSS rescore
  4. 2026-06-21 01:58 UTCEPSS rescore
  5. 2026-06-19 19:24 UTCEPSS rescore
  6. 2026-06-19 19:24 UTCEPSS rescore
  7. 2026-06-18 17:51 UTCEPSS rescore
  8. 2026-06-17 17:51 UTCEPSS rescore
  9. 2026-06-16 17:51 UTCEPSS rescore
  10. 2026-06-16 17:51 UTCEPSS rescore
  11. 2026-06-15 17:47 UTCEPSS rescore
  12. 2026-06-14 23:16 UTCEPSS rescore
  13. 2026-06-13 22:59 UTCEPSS rescore
  14. 2026-06-13 22:59 UTCEPSS rescore
  15. 2026-06-12 23:11 UTCEPSS rescore
  16. 2026-06-11 13:59 UTCEPSS rescore
  17. 2026-06-10 22:17 UTCEPSS rescore
  18. 2026-06-06 13:46 UTCEPSS rescore
  19. 2026-06-06 13:46 UTCEPSS rescore
  20. 2026-06-05 22:46 UTCEPSS rescore
  21. 2026-06-05 22:46 UTCEPSS rescore
  22. 2026-06-05 06:09 UTCEPSS rescore
  23. 2026-06-05 06:09 UTCEPSS rescore
  24. 2026-06-04 13:11 UTCEPSS rescore
  25. 2026-06-04 13:11 UTCEPSS rescore
  26. 2026-06-02 20:12 UTCEPSS rescore
  27. 2026-06-02 20:12 UTCEPSS rescore
  28. 2026-05-31 00:15 UTCEPSS rescore
  29. 2026-05-31 00:15 UTCEPSS rescore
  30. 2026-05-29 13:43 UTCEPSS rescore
  31. 2026-05-28 13:44 UTCEPSS rescore
  32. 2026-05-28 13:44 UTCEPSS rescore
  33. 2026-05-27 13:40 UTCEPSS rescore
  34. 2026-05-27 13:39 UTCEPSS rescore
  35. 2026-05-26 13:43 UTCEPSS rescore
  36. 2026-05-26 13:43 UTCEPSS rescore
  37. 2026-05-26 07:18 UTCEPSS rescore
  38. 2026-05-26 07:18 UTCEPSS rescore
  39. 2026-05-24 13:43 UTCEG score recompute
  40. 2026-05-24 13:43 UTCGHSA enrichment

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2023/CVE-2023-6023.yaml
    First seen Jan 1, 2023

    VertaAI ModelDB - Path Traversal

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-6023?
CVE-2023-6023 is a high vulnerability published on November 16, 2023. An attacker can read any file on the filesystem on the server hosting ModelDB through an LFI in the artifact_path URL parameter.
When was CVE-2023-6023 disclosed?
CVE-2023-6023 was first published in the National Vulnerability Database on November 16, 2023, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-6023 actively exploited?
CVE-2023-6023 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 85.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-6023?
CVE-2023-6023 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.6.
How do I remediate CVE-2023-6023?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-6023, 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

Explore the affected products and dependency analysis for CVE-2023-6023

Explore →

Is Your Infrastructure Affected by CVE-2023-6023?

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

Start Free Scan →Browse All CVEs