UTC
Critical

Remote file access vulnerability in `mlflow server` and `mlflow ui` CLIs

GHSA-83fm-w79m-64r5 · published 2023-05-01

Severity
Critical
CVSS score
Not scored
Chance of exploitation (EPSS)
No CVE
Fixed in
2.3.1
What it is

Users of the MLflow Open Source Project who are hosting the MLflow Model Registry using the commands using an MLflow version older than MLflow 2.3.1 may be vulnerable to a remote file access exploit if they are not limiting who can query their server (for example, by using a cloud VPC, an IP allowlist for inbound requests, or authentication / authorization middleware). This issue only affects users and integrations that run the commands. Integrations that do not make use of are unaffected; for example, the Databricks Managed MLflow product and MLflow on Azure Machine Learning do not make use of these commands and are not impacted by these vulnerabilities in any way.

What to do

Upgrade mlflow to 2.3.1 or later.

This vulnerability has been patched in MLflow 2.3.1, which was released to PyPI on April 27th, 2023. If you are using with the MLflow Model Registry, we recommend upgrading to MLflow 2.3.1 as soon as possible.

If you cannot upgrade yet

If you are using the MLflow open source commands, we strongly recommend limiting who can access your MLflow Model Registry and MLflow Tracking servers using a cloud VPC, an IP allowlist for inbound requests, authentication / authorization middleware, or another access restriction mechanism of your choosing. If you are using the MLflow open source commands, we also strongly recommend limiting the remote files to which your MLflow Model Registry and MLflow Tracking servers have access.

Affected
PackageRegistryAffectedFixed in
mlflowPyPI< 2.3.12.3.1

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].