Servers and applications
GHSA-gqvg-gmmx-x4hm
MLFLOW_ALLOW_PICKLE_DESERIALIZATION=False safety control bypassed by mlflow.statsmodels flavor — RCE via crafted model artifact
- Severity
- High 8.8
- Published
- 27 Jul 2026
- Last changed
- 27 Jul 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 3.15.0
- Attack
- Over the network · No login needed · Needs someone to click or open something
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H- Sources
- Project advisories (GitHub)
Description
MLflow introduced MLFLOW_ALLOW_PICKLE_DESERIALIZATION as a security control to prevent unsafe pickle.load execution during model loading, in response to CVE-2024-37052 through CVE-2024-37060. When set to False, operators expect all pickle deserialization to be blocked. The most recent related fix (#21188) patched a bypass in the pyfunc flavor.
However, the mlflow.statsmodels flavor completely omits this guard. An attacker who places a crafted MLmodel artifact into any accessible artifact store can trigger arbitrary code execution on any process that calls mlflow.pyfunc.load_model() against the malicious model — even when MLFLOW_ALLOW_PICKLE_DESERIALIZATION=False.
This is a security control bypass. The operator believes pickle RCE is mitigated; the statsmodels flavor silently ignores the control.
mlflow.pyfunc.load_model() dispatches to flavor _load_pyfunc implementations via:
The guarded pattern (from mlflow/sklearn/init.py L526-533, the reference implementation) is:
Affected software
| Software | Affected versions |
|---|---|
MLflowServers and applications · github:mlflow/mlflow |
|
About MLflow
Python library
- Monthly downloads
- 30M+MLflow
- Weekly downloads (PyPI)
- 5,332,947PyPI Stats, 15 Nov 2026
- GitHub stars
- 28,816GitHub, 15 Nov 2026
- Forks
- 6,611GitHub, 15 Nov 2026
- Latest release
- v3.18.0GitHub, 15 Nov 2026
- Released
- 4 Nov 2026GitHub
- License
- Apache Software License 2.0Wikidata
- First published on GitHub
- 5 Jun 2018GitHub
Vulnerabilities in MLflow
- In our list
- 89
- Published in the last 12 months
- 37
- Critical, last 12 months
- 7
- High, last 12 months
- 15
- Known exploited
- 1
- CVE-2026-127202MLflow < 3.18.0 Path Traversal via model_id in log_outputs APIMedium 6.3 12 Nov 2026
- CVE-2026-118628Server-Side Request Forgery in the MLflow tracking server via client-supplied artifact locations and model version sourcesHigh 8.2 3 Nov 2026
- CVE-2026-118627MLflow SHAP load_explainer Deserialization of Untrusted Data Remote Code Execution VulnerabilityHigh 7.8 3 Nov 2026
- CVE-2026-118626MLflow Tracking Server Issues Missing Authorization Privilege Escalation VulnerabilityMedium 5.4 3 Nov 2026
- CVE-2026-118625MLflow Tracking Server Missing Authorization Privilege Escalation VulnerabilityMedium 6.3 3 Nov 2026
- CVE-2026-118624MLflow Tracking Server Jobs Missing Authorization Information Disclosure VulnerabilityMedium 5.4 3 Nov 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-gqvg-gmmx-x4hm
- github.com https://github.com/mlflow/mlflow/security/advisories/GHSA-gqvg-gmmx-x4hm