Skip to content
MLflowGHSA-p4jx-q62p-x5jr

MLflow allows low privilege users to delete any artifact

Medium5.4CVE-2024-4263 · Published May 16, 2024 · updated Feb 22, 2026

A broken access control vulnerability exists in mlflow/mlflow versions before 2.10.1, where low privilege users with only EDIT permissions on an experiment can delete any artifacts. This issue arises due to the lack of proper validation for DELETE requests by users with EDIT permissions, allowing them to perform unauthorized deletions of artifacts. The vulnerability specifically affects the handling of artifact deletions within the application, as demonstrated by the ability of a low privilege user to delete a directory inside an artifact using a DELETE request, despite the official documentation stating that users with EDIT permission can only read and update artifacts, not delete them.

GitHub advisory

Affected versions

PackageAffectedFixed in
mlflow
PyPI
< 2.10.12.10.1
Details and references

More MLflow advisories

All MLflow
Advisory
MLFlow unsafe deserialization
High8.8Jun 4, 2024
MLFlow unsafe deserialization
High8.8Jun 4, 2024
MLFlow unsafe deserialization
High8.8Jun 4, 2024
MLFlow unsafe deserialization
High8.8Jun 4, 2024
MLFlow unsafe deserialization
High8.8Jun 4, 2024
MLflow has a Local File Read/Path Traversal bypass
High7.5May 16, 2024

Critical advisories by email

Wednesdays: the week’s critical and high advisories in the AI and data stack, with the fixed versions. Only in weeks that have some.

Double opt-in. Unsubscribe any time.