Skip to main content
VulnerabilityPublished Updated

CVE-2025-15379: MLflow Command Injection vulnerability

Affects mlflowSource GCVE Database

0
Compare
Authoritative record:CVE-2025-15379· Critical 10.0

Not known to be exploited · CVSS 10.0 Critical : upgrade to 3.8.1 as a priority.

Data as of 16 Nov 2026, 16:52 UTC

CVSS 3.0 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.8.1
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade mlflow to 3.8.1.

Affected software

ProductAffectedFixed in
PyPImlflowAffected
  • <3.8.1
Fixed in
  • 3.8.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in MLflow version 3.8.1. Users should upgrade to version 3.8.1 or later to remediate this vulnerability. If upgrading is not immediately possible, avoid deploying models with env_manager=LOCAL. If env_manager=LOCAL must be used, ensure all model artifacts, especially python_env.yaml files, come from trusted and vetted sources to prevent malicious command injection.

Description

CVE-2025-15379 is a critical command injection vulnerability in MLflow versions prior to 3.8.1. It occurs in the model serving container initialization code when deploying models with the env_manager=LOCAL option. The vulnerability arises because MLflow reads dependency specifications from the model artifact's python_env.yaml file and directly interpolates them into a shell command without proper sanitization. This allows an attacker who can supply a malicious model artifact to execute arbitrary commands on the system with the same privileges as the MLflow process. The issue is fixed in MLflow version 3.8.1.

References

Community reviews

Loading reviews…