cve.bz

CVE-2026-116692 mlflow mlflow: Code Injection

9.8 criticalEPSS 0.7%Fix available

Critical (9.8) in mlflow mlflow. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in mlflow 3.17.0.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.7% (unchanged from 0.7% a week ago) estimated probability of exploitation activity in the next 30 days; 54th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-94 Improper Control of Generation of Code (Code Injection)
CWE-470 Use of Externally-Controlled Input to Select Classes or Code (Reflection Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • mlflow (PyPI): fixed in 3.17.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-116692 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116692?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116692?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-116692 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
mlflow>= 3.12.0rc0, < 3.17.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-26p8-2jq9-3vq9PyPImlflow>=3.12.0rc0 <3.17.03.17.0

Attack patterns (CAPEC)

  • CAPEC-138 Reflection Injection Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-242 Code Injection Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON