Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
MLflow versions from 2.1.0 before 3.15.0 are affected. When MLFLOW_ALLOW_PICKLE_DESERIALIZATION is set to False, the mlflow.statsmodels flavor still unpickles model files without checking that setting. An attacker who can place a crafted model artifact in an accessible artifact store can execute arbitrary code in any process that loads that model with mlflow.pyfunc.load_model(). Upgrade to MLflow 3.15.0 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 8.8 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS No score.
Timeline
- 31 Oct 2026, 14:39 UTC First seen by agentprime
- 31 Oct 2026, 14:39 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-gqvg-gmmx-x4hm
- OSV: GHSA-gqvg-gmmx-x4hm
- github.com/mlflow/mlflow/security/advisories/GHSA-gqvg-gmmx-x4hm
- github.com/mlflow/mlflow/pull/24686
- github.com/mlflow/mlflow/commit/38615289094a4b700a20b5d1dbfbe57bdfb0411f
- github.com/mlflow/mlflow
- github.com/mlflow/mlflow/releases/tag/v3.15.0