Third-Party Scorer Deserialization Vulnerability in MLflow by Databricks
CVE-2026-116692

9.8CRITICAL

Key Information:

Vendor

Mlflow

Status
Mlflow
Vendor
CVE Published:
27 October 2026

What is CVE-2026-116692?

A deserialization vulnerability exists in MLflow that allows unauthorized users to execute arbitrary code via misconfigured artifact endpoints. This issue arises because the scoring mechanism accepts third-party module descendants instead of strictly enforcing allowed modules. In environments where authentication is disabled, attackers can exploit this weakness to run malicious code without any credentials. Even in setups with basic authentication, if a user has permissions to create experiments, they can also exploit this vulnerability. The flaw has been addressed in version 3.17.0, which enforces stricter checks on the allowed scorer modules to prevent unauthorized access.

Affected Version(s)

mlflow >= 3.12.0rc0, < 3.17.0

References

https://github.com/mlflow/mlflow/security/advisories/GHSA...
x_refsource_CONFIRM
https://github.com/mlflow/mlflow/pull/25906
x_refsource_MISC
https://github.com/mlflow/mlflow/commit/a732443e695c3c677...
x_refsource_MISC

CVSS V3.1

Score:
9.8
Severity:
CRITICAL
Confidentiality:
High
Integrity:
High
Availability:
High
Attack Vector:
Network
Attack Complexity:
Low
Privileges Required:
None
User Interaction:
None
Scope:
Unchanged

Timeline

  • Vulnerability published

  • Vulnerability Reserved

.