CVE-2024-8859
A public proof of concept exists; no exploitation attested.
- Published2025-03-20
- Fixed in2.16.0
- WeaknessCWE-29
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « 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- 2025-03-2010:15CVE publishedNVD
- 2026-11-1310:34First public proof of conceptPoC-in-GitHub
Versions per branch
OSV · NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.x | ≥ 2.15.1, < 2.16.0 | 2.16.0 | OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.17 | < 2.17.0rc0 | 2.17.0rc0 | OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.15 | = 2.15.1 | no fix published | NVD |
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/mlflowAffected
- < 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
Fix
- Update mlflow to 2.16.0
Advisories and patches
- github.comPatch
Detection
read 2026-11-13 10:35 UTC- Nuclei template
- available ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- CISA-ADP (SSVC)PoC stated2025-03-20
- PoC-in-GitHub1 repository, unverifiedknown since 2026-11-13dexteon/mlflow-dbfs-path-traversal-cve-2024-8859
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-10-23
- CISA-ADPSSVC decisionpoc2025-03-20
- CNACVSS 3.07.5known since 2026-10-23
- CNAweakness (CWE)CWE-29known since 2026-10-23
- FIRST EPSSEPSS score2.8 %2026-11-19
- PoC-in-GitHubproof of concept1known since 2026-11-13
- ProjectDiscoverydetectionread 2026-11-20
- OSVaffected packages—
- GitHub AdvisoriesadvisoryHigh2025-03-21
Identifiers
- BIT-mlflow-2024-8859same flawBitnami · Apache-2.0
- EUVD-2025-6887same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-4rqf-8pfm-p36rsame flawGitHub Advisory Database · CC-BY-4.0
- PYSEC-2026-1638same flawPyPA Advisory Database · CC-BY-4.0
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?
Is CVE-2024-8859 actively exploited?
What is the CVSS score for CVE-2024-8859?
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
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-4rqf-8pfm-p36r
- Nuclei templates · MIT
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- PoC-in-GitHub · CC0-1.0
- CISA Vulnrichment · CC0-1.0