Advisory record · GHSA-p4jx-q62p-x5jr

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 aris...

CVSS 5.4 MediumEPSS 0.0033 · 26th percentile

Published by the GitHub Advisory Database at 16 May 2024, 09:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
mlflowPyPI<b43e0e3de5b500554e13dc032ba2083b2d6c94b8 || <2.10.1b43e0e3de5b500554e13dc032ba2083b2d6c94b8, 2.10.1
Identifiers
GHSA-p4jx-q62p-x5jr · BIT-mlflow-2024-4263 · CVE-2024-4263 · PYSEC-2024-51
Weakness (CWE)
CWE-284
Published
16 May 2024
Updated
10 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

mlflow versions before 2.10.1 are vulnerable to a broken access control flaw in which a user holding only EDIT permission on an experiment can delete artifacts they should not be able to remove. An attacker with such an account can send DELETE requests to delete artifacts, including directories within them, despite documentation limiting EDIT users to reading and updating artifacts. Upgrade mlflow to version 2.10.1 or later.

Written 10 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.4 Medium 3.0 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L CNA (@huntr_ai)
  • CISA KEV Not listed.
  • EPSS 0.0033, the 26th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the GitHub Advisory Database, published 16 May 2024. New records show when each source confirmed them.

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.