Technical impact
A vulnerability exists in the third-party scorer deserialization logic of MLflow between versions 3.12.0rc0 and 3.17.0. The deserialization process accepts any subclass of the predefined list of allowed modules without validating the specific module name. An attacker can upload a malicious Python module to an artifact path that is writable by the MLflow server and then invoke the scorer via the/ajax‑api/3.0/mlflow/scorer/invoke endpoint. The deserialization layer imports the attacker‑supplied module and constructs the class before processing a trace, leading to arbitrary code execution with the permissions of the MLflow server process. The flaw is a classic example of insecure deserialization (CWE‑470) and code injection (CWE‑94).
Affected Systems
The affected product is MLflow, specifically versions 3.12.0rc0 through 3.16.x inclusive. Versions prior to 3.12.0rc0 and 3.17.0 and later are not impacted.
Risk and Exploitability
The CVSS score of 9.8 indicates a critical severity. The lack of an EPSS score means no current data on exploitation probability, but the vulnerability is fully exploitable on authentication‑disabled deployments and requires only minimal privilege on authentication-enabled deployments. Because the flaw allows execution of arbitrary code on the server side, the potential impact on confidentiality, integrity, and availability is total. The vulnerability is not listed in the CISA KEV catalog.
Github GHSA