mediumCVSS 5.4NVD status: Modified

CVE-2024-3099

MLflow: A vulnerability in mlflow/mlflow version 2.11.1 allows attackers to create multiple models with the same name by exploiting URL encoding.

ComponentMLflow
Severitymedium (CVSS 5.4)
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Published (NVD)2024-06-06
Last modified2026-06-17
Affected versions
mlflow all versions
Fixed insee the vendor advisory
WeaknessCWE-475
CISA KEVnot listed

NVD description

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.

Does CVE-2024-3099 hit the version you run?Paste your docker-compose.yml, requirements.txt or package.json. The scanner checks your pinned versions against this CVE and every other one we track for MLflow.
Check my stack

What to do

  • NVD lists no fixed version yet: follow the vendor advisory below and keep MLflow off the public internet until a fix ships.
  • Do not expose the component's API or UI to the internet without authentication in front of it.

Sources

Read more

Other MLflow CVEs

All MLflow CVEs