5.4
Moyenne
CVE-2024-4263 A broken access control vulnerability exists in mlflow/mlflow versions before 2.10.1, where low privilege users with…
Description
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.
Produits et versions touchés
| Produit | Versions touchées | Corrigé en |
|---|---|---|
| mlflow/mlflow 2.10 | premières → < 2.10.1 | 2.10.1 |
Références
- huntr.com huntr.com
- github.com github.com
Chronologie
- Publiée
- Dernière modification
Autres CVE de mlflow/mlflow
Les 55 CVE de mlflow/mlflow →
CVE-2026-8147
In MLflow versions prior to 3.14.0, when running with authentication enabled, the trace API endpoints lack proper…
8.1
Élevée
CVE-2026-4035
A vulnerability in mlflow/mlflow versions prior to 3.11.0 allows for the resolution of environment variables in AI…
9.1
Critique
CVE-2026-3198
MLflow 3.9.0 with basic-auth (`--app-name basic-auth`) fails to enforce authorization checks for multiple Gateway API…
6.5
Moyenne
CVE-2026-2651
A vulnerability in MLflow…
9.0
Critique