CVE-2025-15379
Lfprojects Mlflow command injection
- Published30 Mar 2026
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/security/cve/CVE-2025-15379
- https://bugzilla.redhat.com/show_bug.cgi?id=2452949
- https://github.com/mlflow/mlflow/commit/361b6f620adf98385c6721e384fb5ef9a30bb05e
- https://huntr.com/bounties/dc9c1c20-7879-4050-87df-4d095fe5ca75
- https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-15379.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-15379 being actively exploited?
CVE-2025-15379 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 2.36%.
How severe is CVE-2025-15379?
CVE-2025-15379 has a CVSS 3.1 base score of 10.0, rated critical. EPSS estimates a 2.36% probability of exploitation.
Which products are affected by CVE-2025-15379?
Affected products include Lfprojects Mlflow.
How do I fix CVE-2025-15379?
Upgrade affected software to a fixed version, for example Lfprojects Mlflow 3.8.1 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-15379 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.