CVE-2024-3848

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 77.1%, top 1% 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
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 43%CVSS: 7.5Exploit: NoneExposed: 0

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

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.5(medium)
EPSS
98.6%
KEV
Not listed

Published

May 16, 2024

Last Modified

January 24, 2025

References (4)

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
mlflow0.0.1 ... v0.2.0 (108 versions)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 / 33× 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-11 08:26 UTCEPSS rescore
  2. 2026-07-09 19:09 UTCEPSS rescore
  3. 2026-07-09 19:09 UTCEPSS rescore
  4. 2026-07-08 15:14 UTCEPSS rescore
  5. 2026-07-06 16:26 UTCEPSS rescore
  6. 2026-07-01 15:05 UTCEPSS rescore
  7. 2026-06-28 14:07 UTCEPSS rescore
  8. 2026-06-28 14:06 UTCEPSS rescore
  9. 2026-06-28 04:55 UTCEPSS rescore
  10. 2026-06-28 04:55 UTCEPSS rescore
  11. 2026-06-27 03:07 UTCEPSS rescore
  12. 2026-06-27 03:07 UTCEPSS rescore
  13. 2026-06-26 11:09 UTCOSV refresh
  14. 2026-06-25 13:49 UTCEPSS rescore
  15. 2026-06-23 21:32 UTCEPSS rescore
  16. 2026-06-23 21:32 UTCEPSS rescore
  17. 2026-06-22 14:25 UTCEPSS rescore
  18. 2026-06-22 14:25 UTCEPSS rescore
  19. 2026-06-21 14:55 UTCEPSS rescore
  20. 2026-06-21 01:58 UTCEPSS rescore
  21. 2026-06-21 01:58 UTCEPSS rescore
  22. 2026-06-18 17:52 UTCEPSS rescore
  23. 2026-06-18 17:52 UTCEPSS rescore
  24. 2026-06-17 17:52 UTCEPSS rescore
  25. 2026-06-16 17:52 UTCEPSS rescore
Show 32 more
  1. 2026-06-16 17:52 UTCEPSS rescore
  2. 2026-06-15 17:47 UTCEPSS rescore
  3. 2026-06-14 23:17 UTCEPSS rescore
  4. 2026-06-13 22:59 UTCEPSS rescore
  5. 2026-06-13 22:59 UTCEPSS rescore
  6. 2026-06-13 22:59 UTCEPSS rescore
  7. 2026-06-12 23:11 UTCEPSS rescore
  8. 2026-06-12 23:11 UTCEPSS rescore
  9. 2026-06-11 13:59 UTCEPSS rescore
  10. 2026-06-10 22:18 UTCEPSS rescore
  11. 2026-06-10 13:21 UTCEPSS rescore
  12. 2026-06-08 17:41 UTCOSV refresh
  13. 2026-06-08 14:16 UTCEPSS rescore
  14. 2026-06-08 14:16 UTCEPSS rescore
  15. 2026-06-07 15:24 UTCEPSS rescore
  16. 2026-06-07 15:24 UTCEPSS rescore
  17. 2026-06-06 13:46 UTCEPSS rescore
  18. 2026-06-06 13:46 UTCEPSS rescore
  19. 2026-06-05 22:46 UTCEPSS rescore
  20. 2026-06-05 22:46 UTCEPSS rescore
  21. 2026-06-05 06:09 UTCEPSS rescore
  22. 2026-06-05 06:09 UTCEPSS rescore
  23. 2026-06-04 13:11 UTCEPSS rescore
  24. 2026-06-04 13:11 UTCEPSS rescore
  25. 2026-06-01 13:51 UTCEPSS rescore
  26. 2026-06-01 13:51 UTCEPSS rescore
  27. 2026-05-31 00:16 UTCEPSS rescore
  28. 2026-05-31 00:15 UTCEPSS rescore
  29. 2026-05-29 13:43 UTCEPSS rescore
  30. 2026-05-28 13:44 UTCEPSS rescore
  31. 2026-05-28 13:44 UTCEPSS rescore
  32. 2026-05-24 02:05 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/2024/CVE-2024-3848.yaml
    First seen Jan 1, 2024

    Mlflow < 2.11.0 - Path Traversal

    Open source ↗

Related CVEs(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 in the National Vulnerability Database 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 98.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-3848?
CVE-2024-3848 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2024-3848?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-3848, 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-3848

Explore →

Is Your Infrastructure Affected by CVE-2024-3848?

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

Start Free Scan →Browse All CVEs