MLflow dspy bypasses pickle deserialization control (CVE-2026-96775) | HOL Guard CVE

High · CVSS 8.8CVE-2026-96775

MLflow dspy bypasses pickle deserialization control

Answer in brief

CVE-2026-96775 records a High severity (CVSS 8.8) vulnerability in MLflow dspy bypasses pickle deserialization control. The current sources do not mark it as known exploited. The current feed maps MLflow/MLflow (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 23, 2026Updated Sep 23, 2026Source checked Sep 23, 2026First seen by HOL Sep 23, 2026Material review Sep 23, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.8
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps MLflow/MLflow (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
MLflow/MLflowgeneric	2.0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for MLflow/MLflow.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Sep 23, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 23, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 23, 2026

Sources and claim methodology

Source referencekb.cert.org

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.