# CVE-2025-15031: Path Traversal Vulnerability in mlflow/mlflow

> Attackers can write arbitrary files via crafted tar archives in MLflow, potentially leading to remote code execution in multi-tenant environments.

- **Severity:** High 8.1 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Mar 2026
- **Updated:** 15 Jul 2026
- **Also known as:** BIT-mlflow-2025-15031, GHSA-fhff-qmm8-h2fp, PYSEC-2026-2656

## What is CVE-2025-15031?

CVE-2025-15031 is a high-severity path traversal vulnerability in Lfprojects Mlflow, published on 18 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in MLflow's pyfunc extraction process allows for arbitrary file writes due to improper handling of tar archive entries. Specifically, the use of `tarfile.extractall` without path validation enables crafted tar.gz files containing `..` or absolute paths to escape the intended extraction directory. This issue affects the latest version of MLflow and poses a high/critical risk in scenarios involving multi-tenant environments or ingestion of untrusted artifacts, as it can lead to arbitrary file overwrites and potential remote code execution.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mlflow` | Bitnami | All versions | 3.11.1 |
| `mlflow` | PyPI | All versions | 3.9.0rc0 |
| `mlflow` | PyPI | All versions | 3.9.0rc0 |
| `mlflow` | PyPI | All versions | 3.9.0rc0 |

Products: Lfprojects Mlflow.

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

Upgrade mlflow to a fixed version for your release line: 3.11.1 or 3.9.0rc0.

## Is CVE-2025-15031 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15031 exists.

## 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-15031 and fix it if it is affected.

What it is: CVE-2025-15031 is a high-severity path traversal vulnerability in Lfprojects Mlflow, published on 18 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15031 exists.

Affected packages and fixed versions:
- mlflow (Bitnami): affected all versions; fixed in 3.11.1
- mlflow (PyPI): affected all versions; fixed in 3.9.0rc0
- mlflow (PyPI): affected all versions; fixed in 3.9.0rc0
- mlflow (PyPI): affected all versions; fixed in 3.9.0rc0

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-15031/ (Markdown: https://insights.sbomify.com/CVE-2025-15031/index.md)
```

## Sources

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

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