mlflow · MLflow · published 2026-10-23

CVE-2026-115886MLflow: SSRF on unauthenticated MLflow servers via third-party scorer kwargs in the scorer invoke, register, and GenAI evaluate endpoints

This month Public proof-of-concept exists (SSVC exploitation: poc).

CVE-2026-115886 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.7% chance of exploitation in the next 30 days, higher than 53% of all CVEs. This MLflow vulnerability: CVSS 6.5 (v3.1), attacks can be automated. Fixed upstream in MLflow 3.17.0. Patch in your normal monthly cycle.

Share this

Remediation#

Fixed upstream in MLflow 3.17.0.

Patch events

  1. This monthSecurity release

    AI toolingMLflow

    MLflow security release: 3.17.0

    Upgrade to 3.17.0

    Why: Public proof-of-concept exists (SSVC exploitation: poc).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.7% (53th pct)FIRST EPSS v2026.06.15
CVSS base score6.5 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
CNA / CISA ADP
SSVC exploitationpocCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →