Mlflow: Command Injection when serving models with enable_mlserver=True

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.6 · CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

EPSS

• CVE-2026-0596: 1.39% estimated exploitation activity in the next 30 days; percentile 72.40 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A command injection vulnerability exists in Mlflow when serving a model with enablemlserver=True. The modeluri is embedded directly into a shell command executed via bash -c without proper sanitization. If the modeluri contains shell metacharacters, such as $() or backticks, it allows for command substitution and execution of attacker-controlled commands. This vulnerability affects the latest version of mlflow/mlflow and can lead to privilege escalation if a higher-privileged service serves models from a directory writable by lower-privileged users.

Published by the source

31 Mar 2026, 15:31 UTC

Last modified by the source

29 Jun 2026, 12:26 UTC

Source last checked

26 Oct 2026, 13:41 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-rvhj-8chj-8v3c

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-rvhj-8chj-8v3c

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-rvhj-8chj-8v3c

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-0596

Advisory: Mlflow: Command Injection when serving models with enable_mlserver=True
IDs: CVE-2026-0596, GHSA-rvhj-8chj-8v3c
Record: https://patchnext.com/advisories/cve-2026-0596 (revision 3, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mlflow 3.9.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI mlflow: affected < 3.9.0; fixed in 3.9.0

## Suggested inspection (read-only)
- `python -m pip show mlflow`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mlflow.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-rvhj-8chj-8v3c (GitHub-reviewed advisory GHSA-rvhj-8chj-8v3c lists affected ranges: PyPI mlflow >=0 <3.9.0)
- Verified: https://osv.dev/vulnerability/GHSA-rvhj-8chj-8v3c (OSV record GHSA-rvhj-8chj-8v3c lists affected ranges: PyPI mlflow >=0 <3.9.0 (fixed))

Commands are suggestions: review each one before running it.