mlflow · MLflow · published 2026-10-27
CVE-2026-116690MLflow: Arbitrary file read on unauthenticated MLflow servers via prompt model version source
This month EPSS 1.8% with high severity (CVSS 7.5).
CVE-2026-116690 is not known to be exploited in the wild. EPSS estimates a 1.8% chance of exploitation in the next 30 days, higher than 79% of all CVEs. This MLflow vulnerability: CVSS 7.5 (v3.1), attacks can be automated. Fixed upstream in MLflow 3.17.0. Patch in your normal monthly cycle.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in MLflow 3.17.0.
Patch events
AI toolingMLflow
MLflow security release: 3.17.0
Upgrade to
3.17.0Why: CVE-2026-116690: EPSS 1.8% with high severity (CVSS 7.5).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 1.8% (79th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.5 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- mlflow mlflow
>= 3.10.0, < 3.17.0(affected)
Description (from the CVE record)#
MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. From 3.10.0 until 3.17.0, the prompt branch in _create_model_version() accepts schemeless relative sources because path validation runs only when a source has a URL scheme, and mlflow.prompt.is_prompt is interpreted by tag presence rather than a true value. A remote caller can store a server-local path as the model version artifact location and use /api/2.0/mlflow/model-versions/get-artifact to read files accessible to the MLflow server process. Default unauthenticated servers require no privileges, while basic-auth deployments are exposed to authenticated users who can create registered models. This issue is fixed in version 3.17.0.
Quoted from the CVE Program record.