CVE-2025-15379: MLflow Command Injection vulnerability
Affects mlflowSource GCVE Database
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
- 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:HExploitation evidence
Disclosed: evidence found.
CVE published 30 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| PyPImlflow | Affected
| Fixed in
|
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
- nvd.nist.gov/vuln/detail/CVE-2025-15379 (opens in a new tab)
- github.com/mlflow/mlflow/commit/361b6f620adf98385c6721e384fb5ef9a30bb05e (opens in a new tab)
- github.com/mlflow/mlflow/commit/a22ce7157f646bdce4c95106fc38ccc9ca289205 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-15379 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2452949 (opens in a new tab)
- github.com/mlflow/mlflow (opens in a new tab)
- github.com/pypa/advisory-database/tree/main/vulns/mlflow/PYSEC-2026-423.yaml (opens in a new tab)
- huntr.com/bounties/dc9c1c20-7879-4050-87df-4d095fe5ca75 (opens in a new tab)
- pypi.org/project/mlflow (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-15379.json (opens in a new tab)