Skip to content
MLflowGHSA-8f8q-q2j7-7j2m

Undefined Behavior in mlflow

Medium5.4CVE-2024-3099 · Published Jun 6, 2024 · updated Jul 7, 2026

GitHub advisory

Affected versions

PackageAffectedFixed in
mlflow
PyPI
< 2.11.32.11.3
Details and references

A vulnerability in mlflow/mlflow version 2.11.1 allows attackers to create multiple models with the same name by exploiting URL encoding. This flaw can lead to Denial of Service (DoS) as an authenticated user might not be able to use the intended model, as it will open a different model each time. Additionally, an attacker can exploit this vulnerability to perform data model poisoning by creating a model with the same name, potentially causing an authenticated user to become a victim by using the poisoned model. The issue stems from inadequate validation of model names, allowing for the creation of models with URL-encoded names that are treated as distinct from their URL-decoded counterparts.

CVSS 3.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Severity from
GitHub (reviewed advisory)
Weakness
CWE-475
Also known as
BIT-mlflow-2024-3099, CVE-2024-3099, PYSEC-2026-1645

More MLflow advisories

All MLflow
DateAdvisory
Jun 62024Remote code execution in mlflow
CVE-2024-0520Critical10.0fixed in 2.9.0
Jun 62024Local File Inclusion in mlflow
CVE-2024-2928High7.5fixed in 2.11.3
Jun 42024MLFlow unsafe deserialization
CVE-2024-37060High8.8no fix yet
Jun 42024MLFlow unsafe deserialization
CVE-2024-37058High8.8no fix yet
Jun 42024MLFlow unsafe deserialization
CVE-2024-37057High8.8no fix yet
Jun 42024MLFlow improper input validation
CVE-2024-37061High8.8no fix yet

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.