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

> Remote attackers can execute arbitrary code on MLflow Tracking Server via directory traversal in model creation without authentication.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Oct 2025
- **Updated:** 26 Feb 2026
- **Also known as:** BIT-mlflow-2025-11201, GHSA-5cvj-7rg6-jggj, MINI-hj7f-cq83-3ffj, PYSEC-2026-1640

## What is CVE-2025-11201?

CVE-2025-11201 is a high-severity path traversal vulnerability in Lfprojects Mlflow, published on 29 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-11201?

6 open source packages ship an affected version, including mlflow. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mlflow` | Bitnami | All versions | 3.0.0 |
| `mlflow` | PyPI | All versions | 2.22.4, 3.0.0 |
| `mlflow` | PyPI | All versions | 2.22.4 |
| `mlflow` | PyPI | All versions | 2.22.4 |
| `mlflow` | PyPI | From 3.0.0rc0 | 3.0.0 |
| `mlflow` | PyPI | From 3.0.0rc0 | 3.0.0 |

Products: Lfprojects Mlflow.

## How do I fix CVE-2025-11201?

Upgrade mlflow to a fixed version for your release line: 3.0.0 or 2.22.4.

## Is CVE-2025-11201 being exploited?

There is no known exploitation of CVE-2025-11201 in the wild and no public exploit code.

Public exploit code:

- PoC for MLFlow unauth RCE (github_poc): https://github.com/rmhowe425/POC-CVE-2025-11201

## Other vulnerabilities in Lfprojects Mlflow

- [CVE-2026-64849](https://insights.sbomify.com/CVE-2026-64849/): MLflow Server-Side Request Forgery (critical 9.3, exploited in the wild)
- [CVE-2025-15379](https://insights.sbomify.com/CVE-2025-15379/): Command Injection in mlflow/mlflow (critical 10.0)
- [CVE-2024-0520](https://insights.sbomify.com/CVE-2024-0520/): Remote Code Execution due to Full Controlled File Write in mlflow/mlflow (critical 10.0)
- [CVE-2023-6977](https://insights.sbomify.com/CVE-2023-6977/): Path Traversal: '\..\filename' (critical 10.0)
- [CVE-2023-6709](https://insights.sbomify.com/CVE-2023-6709/): Improper Neutralization of Special Elements Used in a Template Engine in mlflow/mlflow (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11201 and fix it if it is affected.

What it is: CVE-2025-11201 is a high-severity path traversal vulnerability in Lfprojects Mlflow, published on 29 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-11201 in the wild and no public exploit code.

Affected packages and fixed versions:
- mlflow (Bitnami): affected all versions; fixed in 3.0.0
- mlflow (PyPI): affected all versions; fixed in 2.22.4, 3.0.0
- mlflow (PyPI): affected all versions; fixed in 2.22.4
- mlflow (PyPI): affected all versions; fixed in 2.22.4
- mlflow (PyPI): affected from 3.0.0rc0; fixed in 3.0.0
- mlflow (PyPI): affected from 3.0.0rc0; fixed in 3.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-11201/ (Markdown: https://insights.sbomify.com/CVE-2025-11201/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11201
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11201
- OSV: https://osv.dev/vulnerability/CVE-2025-11201

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-11201/
Summaries are generated and may contain mistakes; the official description above is the record.