BIT-mlflow-2026-116692 · mlflow
BIT-mlflow-2026-116692
Full advisory details, affected packages, severity context, and original source.
Affected technology
Affected versions and fixes
Version information comes from OSV, NVD, and the CVE vendor record. Each source may describe a different package, release branch, or platform.
mlflow · Bitnami
OSV- From 3.12.0 (inclusive) · before 3.17.0 (exclusive)
Fixed releases / commits: 3.17.0
Advisory overview
MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. From 3.12.0 until 3.17.0, third-party scorer deserialization in mlflow/genai/scorers/base.py accepts request-selected descendants of THIRD_PARTY_SCORER_ALLOWED_MODULES rather than requiring an exact allowed module. A caller can use MLflow artifact endpoints to place a Python module beneath a writable allowed package and submit its module and class through /ajax-api/3.0/mlflow/scorer/invoke. Scorer.model_validate_json() imports the module and constructs the class before trace processing. Authentication-disabled deployments permit this code execution without credentials, while basic-auth deployments require a principal capable of creating an experiment and run and uploading artifacts. In either configuration, the allowed scorer package must be writable by the server process. This issue is fixed in version 3.17.0.
Also known as
CVE-2026-116692 · GHSA-26p8-2jq9-3vq9
