CVE-2026-116690 · GHSA-m65p-9j7q-6w33
MLflow vulnerable to arbitrary file read on unauthenticated servers via prompt model version source
- Risk score
- 55/100
- CVSS
- 7.5 v3.1
- Published
- 27 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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 in…
- Affected
- mlflow (pip) >= 3.10.0, < 3.17.0
- Fix
- Upgrade mlflow to 3.17.0 or later.
- Exploitation
- No known exploitation
Story map
At a glance
mlflow: Amber, patch this week. MLflow is vulnerable to remote code execution on unauthenticated servers due to third-party scorer deserialization. An attacker can execute code without credentials, or with basic-auth credentials if they can create an experiment and run and upload artifacts.
The flaws
- CVE-2026-116690: MLflow vulnerable to arbitrary file read on unauthenticated servers via prompt model version source (CVSS 7.5)
- CVE-2026-116692: MLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifact modules (CVSS 9.8)
- CVE-2026-53995: MLflow FileStore trace IDs allow path traversal and arbitrary file writes (CVSS 8.2 · EPSS 1%)
- CVE-2026-115886: MLflow: SSRF on unauthenticated MLflow servers via third-party scorer kwargs in the scorer invoke, register, and GenAI evaluate endpoints (CVSS 6.5 · EPSS 0%)
The fix
Upgrade mlflow: 3.17.0 or later on your release line
Who is exposed: {'products': ['MLflow'], 'packages': [{'ecosystem': 'pip', 'name': 'mlflow', 'vulnerable': '>= 3.12.0rc0, < 3.17.0'}]}
Where it stands
- Public proof of concept
Connects to
- Same weakness: Path traversal (CWE-22). 398 other warnings in 30 days
Why it is Yellow
- CVSS 7.5 high
- Remotely exploitable without logging in
- On your watchlist: PyPI
Affected packages
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
| mlflow | pip | >= 3.10.0, < 3.17.0 | 3.17.0 |
References
- https://github.com/mlflow/mlflow/commit/81730a2ce4ebcd60d5d18f68c96f422ad7e30772
- https://github.com/mlflow/mlflow/pull/25870
- https://github.com/mlflow/mlflow/releases/tag/v3.17.0
- https://github.com/mlflow/mlflow/security/advisories/GHSA-m65p-9j7q-6w33
- https://github.com/advisories/GHSA-m65p-9j7q-6w33
- https://github.com/advisories/GHSA-m65p-9j7q-6w33
Original description
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.
Last activity 27 Oct 2026. Patch Forecast updates every hour.