CVE-2024-0520

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 2.4%, top 18% of all CVEs by exploit prediction. 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: epss, nvd
Elevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 8.8Exploit: Elevated riskExposed: 0

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

A vulnerability in mlflow/mlflow version 8.2.1 allows for remote code execution due to improper neutralization of special elements used in an OS command ('Command Injection') within the mlflow.data.http_dataset_source.py module. Specifically, when loading a dataset from a source URL with an HTTP scheme, the filename extracted from the Content-Disposition header or the URL path is used to generate the final file path without proper sanitization. This flaw enables an attacker to control the file path fully by utilizing path traversal or absolute path techniques, such as '../../tmp/poc.txt' or '/tmp/poc.txt', leading to arbitrary file write. Exploiting this vulnerability could allow a malicious user to execute commands on the vulnerable machine, potentially gaining access to data and model information. The issue is fixed in version 2.9.0.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

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
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
83%
KEV
Not listed

Published

June 6, 2024

Last Modified

October 15, 2025

Advisory Details (2)

Auto-updated Aug 30, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

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

https://huntr.com/bounties/93e470d7-b6f0-409b-af63-49d3e2a26dbc
github_commit

commit 400c226953b4 (mlflow/mlflow)

Fix landed in mlflow/mlflow commit 400c226953b4 — awaiting tagged release

https://github.com/mlflow/mlflow/commit/400c226953b4568f4361bc0a0c223511652c2b9d

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
mlflow0.0.1 ... v0.2.0 (96 versions)2.9.0

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 154 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2024-0520?
CVE-2024-0520 is a high vulnerability published on June 6, 2024. A vulnerability in mlflow/mlflow version 8.2.1 allows for remote code execution due to improper neutralization of special elements used in an OS command ('Command Injection') within the mlflow.data.httpdatasetsource.py module. Specifically, when loading a dataset from a source URL with an HTTP…
When was CVE-2024-0520 disclosed?
CVE-2024-0520 was first published in the National Vulnerability Database on June 6, 2024, with the most recent update on October 15, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-0520 actively exploited?
CVE-2024-0520 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 16.7% of all scored CVEs.
What is the CVSS score of CVE-2024-0520?
CVE-2024-0520 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2024-0520?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-0520, 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-2024-0520

Explore →

Is Your Infrastructure Affected by CVE-2024-0520?

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