CVE-2023-6909

HIGHNVD 7.57.5
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: nvd
Elevated
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 90%
CISA-KEV: Not listedEPSS: 90%CVSS: 7.5Exploit: NoneExposed: 0

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

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

CVSS v3
7.5
EG Score
7.5(low)
EPSS
99.8%
KEV
Not listed

Published

December 18, 2023

Last Modified

June 17, 2026

References (4)

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
mlflow0.0.1 ... v0.2.0 (98 versions)2.9.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 18× 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-06 16:26 UTCEPSS rescore
  2. 2026-07-06 16:26 UTCEPSS rescore
  3. 2026-07-06 02:22 UTCEPSS rescore
  4. 2026-07-06 02:22 UTCEPSS rescore
  5. 2026-07-04 06:29 UTCEPSS rescore
  6. 2026-06-28 14:06 UTCEPSS rescore
  7. 2026-06-28 14:06 UTCEPSS rescore
  8. 2026-06-25 13:48 UTCEPSS rescore
  9. 2026-06-25 13:48 UTCEPSS rescore
  10. 2026-06-24 19:31 UTCOSV refresh
  11. 2026-06-23 21:31 UTCEPSS rescore
  12. 2026-06-23 21:31 UTCEPSS rescore
  13. 2026-06-16 17:51 UTCEPSS rescore
  14. 2026-06-16 17:51 UTCEPSS rescore
  15. 2026-06-15 17:47 UTCEPSS rescore
  16. 2026-06-13 22:59 UTCEPSS rescore
  17. 2026-06-13 22:59 UTCEPSS rescore
  18. 2026-06-12 23:11 UTCEPSS rescore
  19. 2026-06-10 13:21 UTCEPSS rescore
  20. 2026-06-07 20:16 UTCOSV refresh
  21. 2026-06-06 13:46 UTCEPSS rescore
  22. 2026-06-06 13:46 UTCEPSS rescore
  23. 2026-06-05 22:46 UTCEPSS rescore
  24. 2026-06-05 22:46 UTCEPSS rescore
  25. 2026-05-31 22:30 UTCEPSS rescore
Show 7 more
  1. 2026-05-31 22:30 UTCEPSS rescore
  2. 2026-05-29 13:43 UTCEPSS rescore
  3. 2026-05-28 13:44 UTCEPSS rescore
  4. 2026-05-28 13:44 UTCEPSS rescore
  5. 2026-05-26 13:43 UTCEPSS rescore
  6. 2026-05-26 13:43 UTCEPSS rescore
  7. 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 ↗

Frequently asked(5)

What is CVE-2023-6909?
CVE-2023-6909 is a high 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 in the National Vulnerability Database 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 99.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-6909?
CVE-2023-6909 has a CVSS v3 base score of 7.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2023-6909?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-6909, 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-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.

Start Free Scan →Browse All CVEs