BaselineWatch
Desk

CVE-2026-115886

6.5 medium Published

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.

Fix

Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.

Change history 4

  1. StatusAwaiting Analysis → PublishedNVD modified 2026-10-29 18:18
  2. StatusPublished → Awaiting AnalysisNVD modified 2026-10-26 18:39
  3. StatusReceived → PublishedNVD modified 2026-10-23 21:17
  4. First seenCVSS 6.5NVD modified 2026-10-23 22:16

Affected (CPE criteria) 0

NVD has not attached CPE configurations yet.

References 4