CVE-2026-96775MLflow dspy bypasses pickle deserialization control
Updated under an hour ago ()
Does this affect you?
It affects MLflow. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 8.8 HIGH (v3.1, CISA ADP)CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Weakness (CWE)
- CWE-502
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- certcc
- NVD analysis
- Deferred
- Record last updated
- Sep 23, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
MLflow MLflow mlflow:mlflow (from the name) | 2.0 | CNA record |
References
- https://kb.cert.org/vuls/id/369093
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.