CVE Tools

CVE-2025-15379

Command Injection in mlflow/mlflow

CVE-2025-15379 is a command injection in Mlflow Mlflow/mlflow (CVSS 10.0, Critical).

No known exploitation. EPSS puts it in the 85th percentile. Fixed versions are out.

Check it yourself

OpenVAS · 1 check

e.g. OID 1.3.6.1.4.1.25623.1.0.133218

Run the check

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • Mlflow/mlflowAffected: ≥ unspecified, < 3.8.2Upgrade to: 3.8.2Stated by: CVE record
  • Lfprojects MlflowAffected: ≥ 3.8.0, < 3.8.1Upgrade to: 3.8.1Stated by: NVD

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

A command injection vulnerability exists in MLflow's model serving container initialization code, specifically in the `_install_model_dependencies_to_env()` function. When deploying a model with `env_manager=LOCAL`, MLflow reads dependency specifications from the model artifact's `python_env.yaml` file and directly interpolates them into a shell command without sanitization. This allows an attacker to supply a malicious model artifact and achieve arbitrary command execution on systems that deploy the model. The vulnerability affects versions 3.8.0 and is fixed in version 3.8.2.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS85th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

2.5% chance of exploitation activity in the next 30 days, which ranks it in the 85th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

10 events over 158 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. Patch availablerecord updated
  4. OpenVAS check added
  5. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Scored 10.0 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Questions about CVE-2025-15379

Is CVE-2025-15379 being exploited?
No exploitation is confirmed and no public exploit is known. EPSS puts the chance of exploitation in the next 30 days at 2.5%.
Which versions are affected by CVE-2025-15379?
Mlflow/mlflow: ≥ unspecified, < 3.8.2. Mlflow: ≥ 3.8.0, < 3.8.1.
How do I fix or mitigate CVE-2025-15379?
Upgrade to a fixed build for your product branch: 3.8.2, 3.8.1. The advisory is on access.redhat.com.

Last updated

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Mlflow/mlflow, not every advisory.