Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
MLflow versions before 2.9.2 are vulnerable to server-side request forgery. An attacker with access to the MLflow server can make it send requests to internal HTTP(s) servers, and the source says this could in the worst case lead to remote code execution on the host, for example on an AWS instance. Upgrade mlflow to version 2.9.2 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 |
|---|---|---|---|---|
| 8.6 | High | 3.0 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N | CNA (@huntr_ai) |
- CISA KEV Not listed.
- EPSS 0.015, the 74th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
Sources
- GitHub Advisory Database: GHSA-59v3-898r-qwhj
- OSV: GHSA-59v3-898r-qwhj
- nvd.nist.gov/vuln/detail/CVE-2023-6974
- github.com/mlflow/mlflow/commit/8174250f83352a04c2d42079f414759060458555
- github.com/mlflow/mlflow
- huntr.com/bounties/438b0524-da0e-4d08-976a-6f270c688393
- pypi.org/project/mlflow
- github.com/advisories/GHSA-59v3-898r-qwhj