MediumGHSA-wp72-7hj9-5265BIT-mlflow-2023-1176CVE-2023-1176PYSEC-2023-28

Remote file existence check vulnerability in `mlflow server` and `mlflow ui` CLIs

Published 24 Mar 2023 · Updated 25 Sept 2024

Is your project on an affected mlflow?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

mlflowPyPI
Affected
<2.2.1
Fixed in
2.2.1
Update to the fixed version for your release line, for example:pip install 'mlflow>=2.2.1'

Details

Impact

Users of the MLflow Open Source Project who are hosting the MLflow Model Registry using the mlflow server or mlflow ui commands using an MLflow version older than MLflow 2.2.1 may be vulnerable to a remote file existence check 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 mlflow server and mlflow ui commands. Integrations that do not make use of mlflow server or mlflow ui 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.

The vulnerability detailed in https://nvd.nist.gov/vuln/detail/CVE-2023-1176 enables an actor to check the existence of arbitrary files unrelated to MLflow from the host server, including any files stored in remote locations to which the host server has access.

Patches

This vulnerability has been patched in MLflow 2.2.1, which was released to PyPI on March 2nd, 2023. If you are using mlflow server or mlflow ui with the MLflow Model Registry, we recommend upgrading to MLflow 2.2.1 as soon as possible.

Workarounds

If you are using the MLflow open source mlflow server or mlflow ui 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 mlflow server or mlflow ui commands, we also strongly recommend limiting the remote files to which your MLflow Model Registry and MLflow Tracking servers have access. For example, if your MLflow Model Registry or MLflow Tracking server uses cloud-hosted blob storage for MLflow artifacts, make sure to restrict the scope of your server's cloud credentials such that it can only access files and directories related to MLflow.

References

More information about the vulnerability is available at https://nvd.nist.gov/vuln/detail/CVE-2023-1176.

Is GHSA-wp72-7hj9-5265 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected mlflow, and gives you the command that fixes it.

More advisories for mlflow

  • HighCVE-2026-116690MLflow vulnerable to arbitrary file read on unauthenticated servers via prompt model version source · 27 Oct 2026
  • MediumCVE-2026-116691MLflow CrewAI autologging records LLM provider API keys in logged trace spans · 27 Oct 2026
  • CriticalCVE-2026-116692MLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifact modules · 27 Oct 2026
  • MediumCVE-2026-115886MLflow: SSRF on unauthenticated MLflow servers via third-party scorer kwargs in the scorer invoke, register, and GenAI evaluate endpoints · 23 Oct 2026
  • HighCVE-2026-53995MLflow FileStore trace IDs allow path traversal and arbitrary file writes · 20 Oct 2026
  • HighGHSA-gqvg-gmmx-x4hmMLFLOW_ALLOW_PICKLE_DESERIALIZATION=False safety control bypassed by mlflow.statsmodels flavor — RCE via crafted model artifact · 1 Sept 2026
All 87 advisories for mlflow

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.