Widely-used MLflow; enables remote code execution via malicious model artifacts, risking outages.
CVE-2025-15379
Critical RCE via MLflow model-serving init; unsanitized python_env.yaml.
Is CVE-2025-15379 being exploited?
Not confirmed. CVE-2025-15379 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 2.4% probability of exploitation in the next 30 days.
How severe is CVE-2025-15379?
CVE-2025-15379 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-15379?
Yes. A fix has been recorded for CVE-2025-15379. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-15379 affect?
CVE-2025-15379 affects MLflow 3.8.0 (LOCAL env) model-serving, MLflow Model Serving deployments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2025-15379?
Upgrade to 3.8.2; redeploy; sanitize env specs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote RCE via unsanitized python_env.yaml during LOCAL deployment; attacker can run commands.
Immediate action required
- affected< 3.8.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.