Vulnerabilities

Vulnerability · CVE-2025-15031

A vulnerability in MLflow's pyfunc extraction process allows for arbitrary file writes due to improper handling of tar archive entries.

Published Mar 18, 2026 · catalog updated Jul 15, 2026 · A vulnerability in MLflow's

Check if you run it

No confirmed exploitation is on record for CVE-2025-15031. EPSS is 0.89%. Act only if a listed version of A vulnerability in MLflow's is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (A vulnerability in MLflow's).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical9.1
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.89%
Remediation
Advisory link
Affected products
cpe lfprojects/mlflow

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 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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe lfprojects/mlflowversion unspecified

How to fix CVE-2025-15031

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-15031. EPSS is 0.89%. Act only if a listed version of A vulnerability in MLflow's is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-22: Path Traversal. EPSS 0.89%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 18, 2026 · NIST NVD

    Detected

    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 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-tena

  2. Jul 15, 2026 · NIST NVD

    Updated

    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 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-tena

Sources

  • CVE.orgVulnerability recordCVE-2025-15031

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-15031

    30-day exploitation probability 0.9%

    first.org
  • NIST NVDVulnerability recordCVE-2025-15031

    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 without path validation enables crafted tar.gz files containing or absolute paths to escape t

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 16, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.