Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
MLflow versions before 2.8.1 allowed arbitrary files to be PUT onto the server. The source gives few details about the required access or attack conditions. Upgrade mlflow to version 2.8.1 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 10.0 | Critical | 3.0 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N | CNA (@huntr_ai) |
- CISA KEV Not listed.
- EPSS 0.049, the 92nd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 16 Nov 2023, 18:30 UTC Confirmed by GitHub Advisory Database
- 16 Nov 2026, 15:45 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-f798-qm4r-23r5
- OSV: GHSA-f798-qm4r-23r5
- nvd.nist.gov/vuln/detail/CVE-2023-6015
- github.com/mlflow/mlflow/pull/10330
- github.com/mlflow/mlflow/commit/cf83dad4df26dd4a850622fe8a51ccab1471a5e7
- github.com/mlflow/mlflow
- github.com/pypa/advisory-database/tree/main/vulns/mlflow/PYSEC-2026-420.yaml
- huntr.com/bounties/43e6fb72-676e-4670-a225-15d6836f65d3
- pypi.org/project/mlflow