# CVE-2026-96775: MLflow dspy bypasses pickle deserialization control

> Remote attackers can execute arbitrary code by bypassing pickle deserialization controls in MLflow's dspy flavor via crafted artifacts.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-q5f3-5gj6-hmj7

## What is CVE-2026-96775?

CVE-2026-96775 is a high-severity unsafe deserialization vulnerability in MLflow, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

MLflow's dspy flavor, versions >= 2.0,  applies the MLFLOW_ALLOW_PICKLE_DESERIALIZATION=False security control only when the model_path ends in .pkl, which allows a remote attacker to execute arbitrary code via a crafted MLmodel artifact.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

No fix has been published for CVE-2026-96775 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-96775 being exploited?

There is no known exploitation of CVE-2026-96775 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96775 is a high-severity unsafe deserialization vulnerability in MLflow, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-96775 in the wild and no public exploit code.

Affected product: MLflow. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-96775/ (Markdown: https://insights.sbomify.com/CVE-2026-96775/index.md)
```

## Sources

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

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