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.
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| mlflow PyPI | < 2.10.1 | 2.10.1 |
Details and references
- CVSS 3.0
- CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-284
- Also known as
- BIT-mlflow-2024-4263, CVE-2024-4263, PYSEC-2024-51
More MLflow advisories
All MLflow| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Jun 42024 | MLFlow unsafe deserialization | High8.8 | No fix yet |
| Jun 42024 | MLFlow unsafe deserialization | High8.8 | No fix yet |
| Jun 42024 | MLFlow unsafe deserialization | High8.8 | No fix yet |
| Jun 42024 | MLFlow unsafe deserialization | High8.8 | No fix yet |
| Jun 42024 | MLFlow unsafe deserialization | High8.8 | No fix yet |
| May 162024 | MLflow has a Local File Read/Path Traversal bypass | High7.5 | 2.12.1 |