Advisory record · GHSA-r23q-823p-vmf7

MLflow Command Injection vulnerability

CVSS 10.0 CriticalCriticalEPSS 0.024 · 84th percentile

Critical, because:

  • CVSS score 10.0: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 30 Mar 2026, 09:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
mlflowPyPI<3.8.13.8.1
Identifiers
GHSA-r23q-823p-vmf7 · BIT-mlflow-2025-15379 · CVE-2025-15379 · PYSEC-2026-423
Weakness (CWE)
CWE-77 · CWE-78
Published
30 Mar 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

MLflow (PyPI package mlflow, versions before 3.8.1) has a command injection flaw in its model serving container initialization code, where dependency specifications read from a model artifact's python_env.yaml are passed into a shell command without sanitization when deploying with env_manager=LOCAL. An attacker who supplies a malicious model artifact could run arbitrary commands on systems that deploy it. Upgrade to mlflow 3.8.1 or later.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
10.0 Critical 3.0 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H CNA (@huntr_ai)
  • CISA KEV Not listed.
  • EPSS 0.024, the 84th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:34 UTC First seen by agentprime
  2. 31 Oct 2026, 14:34 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.