# CVE-2025-11201: PYSEC-2026-1640 - MLflow Tracking Server Model Creation Directory Traversal Remote Code Execution Vulnerability

Source: https://junglewise.ai/threats/cve-2025-11201-mlflow-tracking-server-model-creation-directory-traversal-remote  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-10-29  
License: CC BY 4.0 with a link back

CVE-2025-11201 · Severity: critical · CVSS 9.8 · Published 2025-10-29

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.

Technologies: [mlflow (PyPI)](https://junglewise.ai/threats/technologies/mlflow). Vendors: [Lfprojects](https://junglewise.ai/threats/vendors/lfprojects), [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2025-11201 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-11201 being exploited in the wild.

**How severe is CVE-2025-11201?** Critical severity, with a CVSS score of 9.8, published 29 October 2025.

**Which products and versions are affected?** mlflow (PyPI) ECOSYSTEM:introduced=0,fixed=2.22.4,introduced=3.0.0rc0,fixed=3.0.0, ECOSYSTEM:introduced=3.0.0rc0,fixed=3.0.0.

**Is there a fix for CVE-2025-11201?** Yes. mlflow (PyPI): upgrade to 3.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2025-11201?** Check whether you run Lfprojects Mlflow or mlflow (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- mlflow (PyPI): upgrade to 3.0.0 or later

  ```sh
  pip install "mlflow>=3.0.0"
  ```


## Affected products

- Lfprojects Mlflow
- mlflow (PyPI) ECOSYSTEM:introduced=0,fixed=2.22.4,introduced=3.0.0rc0,fixed=3.0.0, ECOSYSTEM:introduced=3.0.0rc0,fixed=3.0.0

## Identifiers

- CVE-2025-11201
- GHSA-5cvj-7rg6-jggj
- PYSEC-2026-1640

## Related threats

- [MLflow arbitrary code execution in third-party scorer deserialization](https://junglewise.ai/threats/cve-2026-116692-mlflow-is-an-open-source-ai-engineering-platform-for-agents)
- [MLflow credential leak in CrewAI autolog](https://junglewise.ai/threats/cve-2026-116691-mlflow-is-an-open-source-ai-engineering-platform-for-agents)
- [MLflow path traversal in prompt model version artifact access](https://junglewise.ai/threats/cve-2026-116690-mlflow-is-an-open-source-ai-engineering-platform-for-agents)
- [MLflow unsafe deserialization in scorer endpoints](https://junglewise.ai/threats/cve-2026-115886-mlflow-is-an-open-source-ai-engineering-platform-for-agents)
- [MLflow FileStore path traversal in trace storage](https://junglewise.ai/threats/cve-2026-53995-mlflow-3-17-1-and-earlier-contains-a-path-traversal-vulnerability)