Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
MLflow versions before 3.8.0rc0 are vulnerable to a directory traversal flaw in the Tracking Server's artifact handler, caused by missing validation of user-supplied file paths. A remote attacker who needs no authentication can exploit it to execute arbitrary code in the context of the service account. Upgrade mlflow to 3.8.0rc0 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.1 | High | 3.0 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | CNA (zdi) |
- CISA KEV Not listed.
- EPSS 0.018, the 79th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:11 UTC First seen by agentprime
- 31 Oct 2026, 14:11 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-q2r8-vmq7-fpx2
- OSV: GHSA-q2r8-vmq7-fpx2
- nvd.nist.gov/vuln/detail/CVE-2026-2033
- github.com/mlflow/mlflow/pull/19260
- github.com/mlflow/mlflow/commit/5bf2ec2bd4222a18d78631183ac7f6b752afe8a4
- github.com/mlflow/mlflow
- github.com/mlflow/mlflow/releases/tag/v3.8.0rc0
- www.zerodayinitiative.com/advisories/ZDI-26-105