Skip to main content
Public proof of conceptFix available

CVE-2024-8859

A public proof of concept exists; no exploitation attested.

  • Published2025-03-20
  • Fixed in2.16.0
  • WeaknessCWE-29

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A path traversal vulnerability exists in mlflow/mlflow version 2.15.1. When users configure and use the dbfs service, concatenating the URL directly into the file protocol results in an arbitrary file read vulnerability. This issue occurs because only the path part of the URL is checked, while parts such as query and parameters are not handled. The vulnerability is triggered if the user has configured the dbfs service, and during usage, the service is mounted to a local directory.

Timeline

dates in UTC
  1. 2025-03-2010:15CVE publishedNVD
  2. 2026-11-1310:34First public proof of conceptPoC-in-GitHub

Versions per branch

OSV · NVD
mlflow
BranchAffectedFixed in
2.x≥ 2.15.1, < 2.16.02.16.0
mlflow
BranchAffectedFixed in
2.17< 2.17.0rc02.17.0rc0
Lfprojects mlflow
BranchAffectedFixed in
2.15= 2.15.1no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As @huntr_ai, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • mlflow/mlflow
    Affected
    • < 2.17.0fixed in 2.17.0custom

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2025-03-20

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • mlflowTuxCare:PyPIfrom 2.9.1.post0 · fixed in 2.9.1.post4+tuxcare

Full record on NVD

Fix

  1. Update mlflow to 2.16.0

Advisories and patches

Detection

read 2026-11-13 10:35 UTC
Nuclei template
available
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Published
2025-03-20
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-4rqf-8pfm-p36r

Frequently asked questions

What is CVE-2024-8859?

A path traversal vulnerability exists in mlflow/mlflow version 2.15.1. When users configure and use the dbfs service, concatenating the URL directly into the file protocol results in an arbitrary file read vulnerability. This issue occurs because only the path part of the URL is checked, while parts such as query and parameters are not handled. The vulnerability is triggered if the user has configured the dbfs service, and during usage, the service is mounted to a local directory.

Is CVE-2024-8859 actively exploited?

A proof-of-concept exploit exists for CVE-2024-8859, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2024-8859?

CVE-2024-8859 has a CVSS v3 base score of 7.5 (High severity), with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Running mlflow? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record