Skip to content
Fencer Vulns
high 8.1

CVE-2025-11201 in the critical feed json

MLflow Tracking Server Model Creation Directory Traversal Remote Code Execution Vulnerability

published 2025-10-29 12 mo ago modified 2026-10-19 20 d ago also BIT-mlflow-2025-11201 , EUVD-2025-36707 , GHSA-5cvj-7rg6-jggj , PYSEC-2026-1640

cvss
8.1
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
26.3%
EPSS 26.3% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

MLflow Tracking Server Model Creation Directory Traversal Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of MLflow Tracking Server. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the handling of model file paths. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-26921.

Patch / fix

  • pypi mlflow 2.22.4, 3.0.0
  • bitnami mlflow 3.0.0
  • lfprojects mlflow 2025-06-10

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
12 mo ago

Exploit prediction

26.28% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OSV 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi mlflow
>=3.0.0rc0, <3.0.0
<2.22.4
3.0.0
2.22.4
bitnami mlflow
<3.0.0
3.0.0

Affected products

  • MLflow MLflow

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.