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.
CVE-2026-96775
This high-severity CVE scores 8.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(low)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity88% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 23, 2026
Last Modified
September 23, 2026
Advisory Details (1)
Auto-updated Sep 23, 2026VU#369093 - MLflow dspy and statsmodels flavors bypass pickle deserialization control
https://kb.cert.org/vuls/id/369093Vendor Advisories for CVE-2026-96775(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-23 18:17 UTCEG score recompute▲ 8.80
- 2026-09-23 18:17 UTCNVD updateCVSS v3 → 8.8 · severity → HIGH
- 2026-09-23 17:59 UTCEG score recompute▼ 8.80
- 2026-09-23 17:58 UTCNVD update
- 2026-09-23 17:29 UTCEG score recompute▲ 8.80
- 2026-09-23 17:29 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
- 2026-09-23 17:18 UTCNVD update
- 2026-09-23 16:40 UTCEG score recompute
- 2026-09-23 16:39 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-502
Frequently asked(4)
What is CVE-2026-96775?
When was CVE-2026-96775 disclosed?
What is the CVSS score of CVE-2026-96775?
How do I remediate CVE-2026-96775?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-96775
Is Your Infrastructure Affected by CVE-2026-96775?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.