# CVE-2026-0596: Command Injection in mlflow/mlflow

> Attackers can execute arbitrary commands via unsanitized model URIs when serving models with MLServer enabled, potentially escalating privileges.

- **Severity:** Critical 9.6 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Mar 2026
- **Updated:** 1 Apr 2026
- **Also known as:** BIT-mlflow-2026-0596, GHSA-rvhj-8chj-8v3c, MINI-p4jm-5v9f-3whq, PYSEC-2026-424

## What is CVE-2026-0596?

CVE-2026-0596 is a critical command injection vulnerability in Lfprojects Mlflow, published on 31 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A command injection vulnerability exists in mlflow/mlflow when serving a model with `enable_mlserver=True`. The `model_uri` is embedded directly into a shell command executed via `bash -c` without proper sanitization. If the `model_uri` 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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-0596?

4 open source packages ship an affected version, including mlflow. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mlflow` | Bitnami | All versions | 3.11.1 |
| `mlflow` | PyPI | All versions | 3.9.0 |
| `mlflow` | PyPI | All versions | 3.9.0 |
| `mlflow` | PyPI | All versions | 3.9.0 |

Products: Lfprojects Mlflow.

## How do I fix CVE-2026-0596?

Upgrade mlflow to a fixed version for your release line: 3.11.1 or 3.9.0.

## Is CVE-2026-0596 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0596 exists.

Public exploit code:

- Research environment and validation scripts for evaluating deserialization behaviors in MLflow and MLServer. (github_poc): https://github.com/SparshBiswas-AI/CVE-2026-0596-Reproduction

## Other vulnerabilities in Lfprojects Mlflow

- [CVE-2026-64849](https://insights.sbomify.com/CVE-2026-64849/): MLflow Server-Side Request Forgery (critical 9.3, exploited in the wild)
- [CVE-2025-15379](https://insights.sbomify.com/CVE-2025-15379/): Command Injection in mlflow/mlflow (critical 10.0)
- [CVE-2024-0520](https://insights.sbomify.com/CVE-2024-0520/): Remote Code Execution due to Full Controlled File Write in mlflow/mlflow (critical 10.0)
- [CVE-2023-6977](https://insights.sbomify.com/CVE-2023-6977/): Path Traversal: '\..\filename' (critical 10.0)
- [CVE-2023-6709](https://insights.sbomify.com/CVE-2023-6709/): Improper Neutralization of Special Elements Used in a Template Engine in mlflow/mlflow (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0596 and fix it if it is affected.

What it is: CVE-2026-0596 is a critical command injection vulnerability in Lfprojects Mlflow, published on 31 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0596 exists.

Affected packages and fixed versions:
- mlflow (Bitnami): affected all versions; fixed in 3.11.1
- mlflow (PyPI): affected all versions; fixed in 3.9.0
- mlflow (PyPI): affected all versions; fixed in 3.9.0
- mlflow (PyPI): affected all versions; fixed in 3.9.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0596/ (Markdown: https://insights.sbomify.com/CVE-2026-0596/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0596
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0596
- OSV: https://osv.dev/vulnerability/CVE-2026-0596

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0596/
Summaries are generated and may contain mistakes; the official description above is the record.