CVE-2023-3765

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 68% (99th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Weaponized
10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 68%
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 68%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.5.0.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
87
EG Risk 87/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)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation68% × 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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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
68%
EPSS %ILE
99th
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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
68% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

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 (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

July 19, 2023

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Oct 17, 2026
Patch available. Sources: github_commit.
Web page

huntr - The world's first bug bounty platform for AI/ML

https://huntr.dev/bounties/4be5fd63-8a0a-490d-9ee1-f33dc768ed76
GitHub commit

commit 6dde93758d42 (mlflow/mlflow)

Fix landed in mlflow/mlflow commit 6dde93758d42 — awaiting tagged release

https://github.com/mlflow/mlflow/commit/6dde93758d42455cb90ef324407919ed67668b9b

Affected Packages

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 34× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 84 of 135 refreshes 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. 16 repeat rows among the latest 100 are merged into the row they repeat. The 51 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:29 UTCEPSS rescoreEPSS 68% · 99th percentile
  2. 2026-10-22 17:20 UTCEG score recompute
  3. 2026-10-22 16:31 UTCEPSS rescoreEPSS 68% · 99th percentile
  4. 2026-10-21 18:45 UTCEG score recompute
  5. 2026-10-21 16:29 UTCEPSS rescoreEPSS 68% · 99th percentile
  6. 2026-10-20 20:32 UTCEG score recompute
  7. 2026-10-20 16:30 UTCEPSS rescoreEPSS 68% · 99th percentile
  8. 2026-10-19 22:20 UTCEG score recompute
  9. 2026-10-19 16:29 UTCEPSS rescoreEPSS 68% · 99th percentile
  10. 2026-10-18 21:10 UTCEG score recompute
  11. 2026-10-18 16:29 UTCEPSS rescoreEPSS 68% · 99th percentile
  12. 2026-10-18 07:56 UTCEG score recompute
  13. 2026-10-17 22:45 UTCEG score recompute
  14. 2026-10-17 00:30 UTCEG score recompute
  15. 2026-10-16 16:36 UTCEPSS rescoreEPSS 68% · 99th percentile
  16. 2026-10-16 00:03 UTCEG score recompute
  17. 2026-10-15 16:29 UTCEPSS rescoreEPSS 68% · 99th percentile
  18. 2026-10-14 16:30 UTCEPSS rescoreEPSS 68% · 99th percentile
  19. 2026-10-14 16:05 UTCEG score recompute
  20. 2026-10-13 16:30 UTCEPSS rescoreEPSS 68% · 99th percentile
  21. 2026-10-12 16:57 UTCEG score recompute
  22. 2026-10-11 21:49 UTCEG score recompute
  23. 2026-10-11 13:45 UTCEPSS rescoreEPSS 68% · 99th percentile
  24. 2026-10-09 20:05 UTCEPSS rescoreEPSS 68% · 99th percentile
  25. 2026-10-08 17:06 UTCEPSS rescoreEPSS 68% · 99th percentile
Show 59 more
  1. 2026-10-07 23:46 UTCEPSS rescoreEPSS 68% · 99th percentile
  2. 2026-10-06 15:15 UTCEPSS rescoreEPSS 68% · 99th percentile
  3. 2026-10-03 14:23 UTCEPSS rescoreEPSS 68% · 99th percentile
  4. 2026-10-01 19:48 UTCEPSS rescoreEPSS 68% · 99th percentile
  5. 2026-09-30 16:27 UTCEG score recompute
  6. 2026-09-30 15:01 UTCEPSS rescoreEPSS 68% · 99th percentile
  7. 2026-09-27 13:42 UTCEPSS rescoreEPSS 68% · 99th percentile
  8. 2026-09-26 15:56 UTCEPSS rescoreEPSS 68% · 99th percentile
  9. 2026-09-24 14:01 UTCEPSS rescoreEPSS 68% · 99th percentile
  10. 2026-09-23 04:02 UTCOSV refresh
  11. 2026-09-18 19:25 UTCEPSS rescoreEPSS 68% · 99th percentile
  12. 2026-09-17 19:25 UTCEPSS rescoreEPSS 68% · 99th percentile
  13. 2026-09-16 14:06 UTCEPSS rescoreEPSS 68% · 99th percentile
  14. 2026-09-16 05:11 UTCEPSS rescoreEPSS 68% · 99th percentile
  15. 2026-09-13 16:44 UTCEPSS rescoreEPSS 68% · 99th percentile
  16. 2026-09-12 14:58 UTCEPSS rescoreEPSS 68% · 99th percentile
  17. 2026-09-11 09:34 UTCEPSS rescoreEPSS 68% · 99th percentile
  18. 2026-09-08 21:58 UTCEPSS rescoreEPSS 68% · 99th percentile
  19. 2026-09-06 13:45 UTCEPSS rescoreEPSS 68% · 99th percentile
  20. 2026-09-05 15:26 UTCEPSS rescoreEPSS 68% · 99th percentile
  21. 2026-09-04 13:58 UTCEPSS rescoreEPSS 68% · 99th percentile
  22. 2026-09-04 05:04 UTCEPSS rescoreEPSS 68% · 99th percentile
  23. 2026-09-03 22:59 UTCOSV refresh
  24. 2026-09-02 14:09 UTCEPSS rescoreEPSS 68% · 99th percentile
  25. 2026-08-30 19:15 UTCEPSS rescoreEPSS 68% · 99th percentile
  26. 2026-08-30 01:20 UTCEPSS rescoreEPSS 68% · 99th percentile
  27. 2026-08-28 21:39 UTCEPSS rescoreEPSS 68% · 99th percentile
  28. 2026-08-27 14:23 UTCEPSS rescoreEPSS 68% · 99th percentile
  29. 2026-08-26 14:43 UTCEPSS rescoreEPSS 68% · 99th percentile
  30. 2026-08-21 23:47 UTCEPSS rescoreEPSS 68% · 99th percentile
  31. 2026-08-20 22:53 UTCEPSS rescoreEPSS 68% · 99th percentile
  32. 2026-08-19 17:02 UTCEPSS rescoreEPSS 68% · 99th percentile
  33. 2026-08-17 13:45 UTCEPSS rescoreEPSS 68% · 99th percentile
  34. 2026-08-17 12:16 UTCOSV refresh
  35. 2026-08-16 02:12 UTCEPSS rescoreEPSS 68% · 99th percentile
  36. 2026-08-13 21:58 UTCEPSS rescoreEPSS 68% · 99th percentile
  37. 2026-08-12 13:48 UTCEPSS rescoreEPSS 68% · 99th percentile
  38. 2026-08-11 13:39 UTCEPSS rescoreEPSS 68% · 99th percentile
  39. 2026-08-07 16:25 UTCEPSS rescoreEPSS 68% · 99th percentile
  40. 2026-08-06 13:45 UTCEPSS rescoreEPSS 68% · 99th percentile
  41. 2026-08-05 19:15 UTCEPSS rescoreEPSS 68% · 99th percentile
  42. 2026-08-02 06:45 UTCOSV refresh
  43. 2026-07-30 16:26 UTCEPSS rescoreEPSS 67% · 99th percentile
  44. 2026-07-30 01:28 UTCEPSS rescoreEPSS 67% · 99th percentile
  45. 2026-07-28 15:34 UTCEPSS rescoreEPSS 67% · 99th percentile
  46. 2026-07-26 14:52 UTCEPSS rescoreEPSS 67% · 99th percentile
  47. 2026-07-25 14:16 UTCEPSS rescoreEPSS 67% · 99th percentile
  48. 2026-07-24 14:16 UTCEPSS rescoreEPSS 67% · 99th percentile
  49. 2026-07-23 14:16 UTCEPSS rescoreEPSS 67% · 99th percentile
  50. 2026-07-23 02:24 UTCEG score recompute
  51. 2026-07-22 23:11 UTCEG score recompute
  52. 2026-07-22 14:06 UTCEPSS rescoreEPSS 67% · 99th percentile
  53. 2026-07-21 15:23 UTCEPSS rescoreEPSS 67% · 99th percentile
  54. 2026-07-20 17:06 UTCEPSS rescoreEPSS 67% · 99th percentile
  55. 2026-07-19 14:29 UTCEPSS rescoreEPSS 71% · 99th percentile
  56. 2026-07-19 02:27 UTCEPSS rescoreEPSS 71% · 99th percentile
  57. 2026-07-18 10:03 UTCEPSS rescoreEPSS 71% · 99th percentile
  58. 2026-07-16 17:01 UTCEPSS rescoreEPSS 71% · 99th percentile
  59. 2026-07-15 16:56 UTCEPSS rescoreEPSS 71% · 99th percentile

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2023/CVE-2023-3765.yaml
    Published Jul 21, 2023

    MLflow Absolute Path Traversal

    Open source ↗

Frequently asked(5)

What is CVE-2023-3765?
CVE-2023-3765 is a critical-severity vulnerability; its CVE record was published on July 19, 2023. Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.5.0.
When was the CVE record for CVE-2023-3765 published?
The CVE record for CVE-2023-3765 was published on July 19, 2023. 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-3765 actively exploited?
CVE-2023-3765 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: CISA's SSVC data says a public PoC exists and its EPSS is 50% or more. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 68% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-3765?
CVE-2023-3765 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2023-3765?
A fix for CVE-2023-3765 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-3765

Explore →

Is Your Infrastructure Affected by CVE-2023-3765?

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