Is CVE-2025-15031 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-15031 being exploited in the wild.

How severe is CVE-2025-15031?

Critical severity, with a CVSS score of 9.1, published 18 March 2026.

Which products and versions are affected?

mlflow (PyPI) ECOSYSTEM:introduced=0,fixed=3.9.0rc0.

Is there a fix for CVE-2025-15031?

Yes. mlflow (PyPI): upgrade to 3.9.0rc0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-15031 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2025-15031?

Check whether you run 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.

CVE-2025-15031: MLflow path traversal in pyfunc extraction

CVE-2025-15031 · Severity: critical · CVSS 9.1 · Published 2026-03-18

MLflow is an open-source platform used by organizations to manage the machine learning lifecycle, including model tracking and deployment. A security flaw in how it handles model files allows an attacker to write malicious files to any location on the server's disk. This could lead to a complete system takeover, data theft, or disruption of machine learning operations, especially in environments where multiple teams share the same infrastructure.

Technologies: mlflow (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2025-15031 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-15031 being exploited in the wild.
How severe is CVE-2025-15031?: Critical severity, with a CVSS score of 9.1, published 18 March 2026.
Which products and versions are affected?: mlflow (PyPI) ECOSYSTEM:introduced=0,fixed=3.9.0rc0.
Is there a fix for CVE-2025-15031?: Yes. mlflow (PyPI): upgrade to 3.9.0rc0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-15031 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-15031?: Check whether you run 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.9.0rc0 or later
```
pip install "mlflow>=3.9.0rc0"
```

Technical details

A path traversal vulnerability (CWE-22) exists in MLflow's pyfunc extraction process due to the insecure use of 'tarfile.extractall' without proper path validation. An attacker can provide a specially crafted tar.gz archive containing entries with '..' sequences or absolute paths to escape the intended extraction directory. This allows for arbitrary file overwrites on the host system. In multi-tenant environments or when ingesting untrusted artifacts, this can be leveraged to achieve remote code execution. The vulnerability affects MLflow versions up to 3.10.1 and has been identified in downstream products like Red Hat OpenShift AI.

Affected products

LF Projects MLflow up to and including 3.10.1
Red Hat OpenShift AI (RHOAI) unspecified

Identifiers

CVE-2025-15031
GHSA-fhff-qmm8-h2fp
PYSEC-2026-2656

Timeline

2026-03-18: disclosed: Vulnerability reported via huntr.dev
2026-03-18: advisory: Initial CVE publication

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.