CVE-2026-116692

Versions, checked against NVD

NVD's record (status: Awaiting Analysis) lists no affected versions of MLflow for this CVE. The ranges above come from the GitHub-reviewed advisory GHSA-26p8-2jq9-3vq9.

NVD description

MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. From 3.12.0rc0 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.

What to do

• Upgrade MLflow to 3.17.0 or later.
• Do not expose the component's API or UI to the internet without authentication in front of it.

Sources

• NVD: CVE-2026-116692
• https://github.com/mlflow/mlflow/commit/a732443e695c3c677680c54320efc394c81654ab
• https://github.com/mlflow/mlflow/pull/25906
• https://github.com/mlflow/mlflow/releases/tag/v3.17.0
• https://github.com/mlflow/mlflow/security/advisories/GHSA-26p8-2jq9-3vq9

Read more

• MLflow authorization CVEs 2026