CVE-2026-115886mlflow >= 3.12.0rc0, Use of Externally-Controlled Input to Select Classes or Code (Unsafe Reflection)
NVDCVSS scored by security-advisories@github.com
Vulnerability Summary
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, the scorer invoke, register, and GenAI evaluate endpoints, including unauthenticated POST /ajax-api/3.0/mlflow/scorer/invoke, accept serialized third-party scorer data that Scorer.model_validate_json resolves using a module-path allowlist without constraining the selected class or its constructor arguments. When optional trulens and trulens-providers-litellm packages are installed, an attacker can select mlflow.genai.scorers.trulens, choose a model URI outside MLflow's native provider registry so execution uses the LiteLLM fallback, and supply api_base and api_key values that cause the server to send an outbound request to an attacker-chosen or internal host with attacker-controlled headers and body. The vulnerable deserialization occurs before a tracking-store lookup or job submission. This issue is fixed in version 3.17.0.
CVSS v3.1 Base Metrics — Score 6.5 (MEDIUM)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NAttack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityLow
IntegrityLow
AvailabilityNone
Affected & Patched Versions
- mlflow >= 3.12.0rc0, < 3.17.0
No patched version published yet
Until a fix ships, reduce exposure:
- Restrict access to the affected service or interface to trusted networks.
- Disable the affected feature if you do not need it.
- Watch the vendor advisory for a firmware or software update.
What to do
Prioritize this fix. Exploit code is public, so attacks can follow quickly.
- Check whether you run mlflow >= 3.12.0rc0, and which version.
- No patched version is listed yet. Limit access to the affected service to trusted networks, and disable the feature if you can.
- Subscribe to the vendor advisory so you learn when a fix ships.
- Review logs and exposed services for signs of earlier compromise.
Timeline
- Oct 23, 2026Published
- Oct 29, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new mlflow >= 3.12.0rc0, CVEsYou are reading CVE-2026-115886. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsExternal References
- Patchhttps://github.com/mlflow/mlflow/commit/bac30b4148c4f40045b4d4db07ae60ab3838803f
- Patchhttps://github.com/mlflow/mlflow/pull/25890
- Referencehttps://github.com/mlflow/mlflow/releases/tag/v3.17.0
- Vendor Advisoryhttps://github.com/mlflow/mlflow/security/advisories/GHSA-2wqp-q3c6-ccj5
- Vendor Advisoryhttps://github.com/mlflow/mlflow/security/advisories/GHSA-2wqp-q3c6-ccj5
Data last checked: Nov 22, 2026 23:12 UTC