CVE-2023-6909

CRITICALNVD 7.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 90% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: epss, nvd
Elevated
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 90%
CISA-KEV: Not listedEPSS PROB: 90%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2.

CVSS v3
7.5
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100CISA SSVC

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
Severity90% × 45%
Exploitation90% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
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
90%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or 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 public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

December 18, 2023

Last Modified

June 17, 2026

References (4)

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
mlflow0.0.1 ... v0.2.0 (98 versions)
  • every version up to 2.9.2: fixed in 2.9.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 2× in last 7d / 13× 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-10-09 20:05 UTCEPSS rescore
  2. 2026-10-06 15:15 UTCEPSS rescore
  3. 2026-09-30 19:40 UTCOSV refresh
  4. 2026-09-30 16:39 UTCEG score recompute
  5. 2026-09-30 15:01 UTCEPSS rescore
  6. 2026-09-30 15:01 UTCEPSS rescore
  7. 2026-09-24 14:01 UTCEPSS rescore
  8. 2026-09-24 14:01 UTCEPSS rescore
  9. 2026-09-20 20:14 UTCEPSS rescore
  10. 2026-09-20 20:14 UTCEPSS rescore
  11. 2026-09-12 14:58 UTCEPSS rescore
  12. 2026-09-12 02:10 UTCOSV refresh
  13. 2026-09-11 09:34 UTCEPSS rescore
  14. 2026-09-07 15:59 UTCEPSS rescore
  15. 2026-09-06 13:46 UTCEPSS rescore
  16. 2026-09-05 15:26 UTCEPSS rescore
  17. 2026-09-01 04:36 UTCEPSS rescore
  18. 2026-08-30 19:15 UTCEPSS rescore
  19. 2026-08-28 21:39 UTCEPSS rescore
  20. 2026-08-26 14:44 UTCEPSS rescore
  21. 2026-08-24 07:57 UTCOSV refresh
  22. 2026-08-21 23:47 UTCEPSS rescore
  23. 2026-08-13 21:58 UTCEPSS rescore
  24. 2026-08-11 13:40 UTCEPSS rescore
  25. 2026-08-09 13:44 UTCEPSS rescore
Show 46 more
  1. 2026-08-08 04:19 UTCOSV refresh
  2. 2026-07-30 16:26 UTCEPSS rescore
  3. 2026-07-28 15:34 UTCEPSS rescore
  4. 2026-07-28 15:34 UTCEPSS rescore
  5. 2026-07-24 14:16 UTCEPSS rescore
  6. 2026-07-23 02:30 UTCEG score recompute
  7. 2026-07-22 21:20 UTCEG score recompute▲ 1.50
  8. 2026-07-22 14:07 UTCEPSS rescore
  9. 2026-07-22 14:07 UTCEPSS rescore
  10. 2026-07-20 17:06 UTCEPSS rescore
  11. 2026-07-19 02:27 UTCEPSS rescore
  12. 2026-07-19 02:27 UTCEPSS rescore
  13. 2026-07-15 16:56 UTCEPSS rescore
  14. 2026-07-13 06:38 UTCOSV refresh
  15. 2026-07-06 16:26 UTCEPSS rescore
  16. 2026-07-06 16:26 UTCEPSS rescore
  17. 2026-07-06 02:22 UTCEPSS rescore
  18. 2026-07-06 02:22 UTCEPSS rescore
  19. 2026-07-04 06:29 UTCEPSS rescore
  20. 2026-06-28 14:06 UTCEPSS rescore
  21. 2026-06-28 14:06 UTCEPSS rescore
  22. 2026-06-25 13:48 UTCEPSS rescore
  23. 2026-06-25 13:48 UTCEPSS rescore
  24. 2026-06-24 19:31 UTCOSV refresh
  25. 2026-06-23 21:31 UTCEPSS rescore
  26. 2026-06-23 21:31 UTCEPSS rescore
  27. 2026-06-16 17:51 UTCEPSS rescore
  28. 2026-06-16 17:51 UTCEPSS rescore
  29. 2026-06-15 17:47 UTCEPSS rescore
  30. 2026-06-13 22:59 UTCEPSS rescore
  31. 2026-06-13 22:59 UTCEPSS rescore
  32. 2026-06-12 23:11 UTCEPSS rescore
  33. 2026-06-10 13:21 UTCEPSS rescore
  34. 2026-06-07 20:16 UTCOSV refresh
  35. 2026-06-06 13:46 UTCEPSS rescore
  36. 2026-06-06 13:46 UTCEPSS rescore
  37. 2026-06-05 22:46 UTCEPSS rescore
  38. 2026-06-05 22:46 UTCEPSS rescore
  39. 2026-05-31 22:30 UTCEPSS rescore
  40. 2026-05-31 22:30 UTCEPSS rescore
  41. 2026-05-29 13:43 UTCEPSS rescore
  42. 2026-05-28 13:44 UTCEPSS rescore
  43. 2026-05-28 13:44 UTCEPSS rescore
  44. 2026-05-26 13:43 UTCEPSS rescore
  45. 2026-05-26 13:43 UTCEPSS rescore
  46. 2026-05-23 10:08 UTCEG score recompute

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-6909.yaml
    First seen Jan 1, 2023

    Mlflow <2.9.2 - Path Traversal

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2023-6909?
CVE-2023-6909 is a critical vulnerability published on December 18, 2023. Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2.
When was CVE-2023-6909 disclosed?
CVE-2023-6909 was first published on December 18, 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-6909 actively exploited?
CVE-2023-6909 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 90% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-6909?
CVE-2023-6909 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2023-6909?
A fix for CVE-2023-6909 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-6909

Explore →

Is Your Infrastructure Affected by CVE-2023-6909?

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

Book a Demo →Browse All CVEs