| Component | MLflow |
| Severity | high (CVSS 7.5) |
| CVSS vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| Published (NVD) | 2026-10-27 |
| Last modified | 2026-10-28 |
| Affected versions | >= 3.10.0, < 3.17.0 from the GitHub-reviewed advisory GHSA-m65p-9j7q-6w33 |
| Fixed in | 3.17.0 |
| Weakness | CWE-22 |
| CISA KEV | not listed |
Versions, checked against NVD
NVD's record (status: Awaiting Analysis) lists no affected versions of MLflow for this CVE. The ranges above come from the GitHub-reviewed advisory GHSA-m65p-9j7q-6w33.
NVD 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.
What to do
- Upgrade MLflow to
3.17.0or later. - Do not expose the component's API or UI to the internet without authentication in front of it.
Sources
- NVD: CVE-2026-116690
- 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