CVE-2024-3848

HIGHNVD 7.57.9▲
EchelonGraph scoreHIGH confidence

Score elevated to 7.9 because EPSS predicts 43% probability of exploitation within the next 30 days (98th 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
7.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 43%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

A path traversal vulnerability exists in mlflow/mlflow version 2.11.0, identified as a bypass for the previously addressed CVE-2023-6909. The vulnerability arises from the application's handling of artifact URLs, where a '#' character can be used to insert a path into the fragment, effectively skipping validation. This allows an attacker to construct a URL that, when processed, ignores the protocol scheme and uses the provided path for filesystem access. As a result, an attacker can read arbitrary files, including sensitive information such as SSH and cloud keys, by exploiting the way the application converts the URL into a filesystem path. The issue stems from insufficient validation of the fragment portion of the URL, leading to arbitrary file read through path traversal.

CVSS v3
7.5
EG Score
7.9HIGHhigh confidence
EG Risk
68
EG Risk 68/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
Severity79% × 45%
Exploitation43% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; 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
43%
EPSS %ILE
98th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; 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 (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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

May 16, 2024

Last Modified

January 24, 2025

References (4)

Affected Packages

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 23× 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 137 total refreshes for this CVE.

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

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/2024/CVE-2024-3848.yaml
    First seen Jan 1, 2024

    Mlflow < 2.11.0 - Path Traversal

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-3848?
CVE-2024-3848 is a high vulnerability published on May 16, 2024. A path traversal vulnerability exists in mlflow/mlflow version 2.11.0, identified as a bypass for the previously addressed CVE-2023-6909. The vulnerability arises from the application's handling of artifact URLs, where a '#' character can be used to insert a path into the fragment, effectively…
When was CVE-2024-3848 disclosed?
CVE-2024-3848 was first published on May 16, 2024, with the most recent update on January 24, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-3848 actively exploited?
CVE-2024-3848 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 43% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-3848?
CVE-2024-3848 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.9 (HIGH).
How do I remediate CVE-2024-3848?
A fix for CVE-2024-3848 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-2024-3848

Explore →

Is Your Infrastructure Affected by CVE-2024-3848?

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

Book a Demo →Browse All CVEs