Skip to content

GHSA-8f8q-q2j7-7j2m BIT-mlflow-2024-3099 CVE-2024-3099 PYSEC-2026-1645

Undefined Behavior in mlflow

Medium PyPI
Severity
5.4 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.44%
Chance of exploitation in the next 30 days. Higher than 38.41% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-475 Undefined Behavior for Input to API
Fix
2.11.3
Upgrade mlflow to this version or later

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.

Affected versions

PyPI

PackageVulnerableFixed in
mlflow
< 2.11.3
2.11.3

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

mlflow PyPI → 2.11.3

pip
pip install --upgrade "mlflow>=2.11.3"
poetry
poetry add "mlflow>=2.11.3"
uv
uv add "mlflow>=2.11.3"

Severity breakdown

CVSS 3.1 5.4

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

Weakness

CWE-475: Undefined Behavior for Input to API

The behavior of this function is undefined unless its control parameter is set to a specific value.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-7gwp-5pfp-969j
MLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebinding)
Critical Known exploited Also affects mlflow
GHSA-26p8-2jq9-3vq9
MLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifact modules
Critical Also affects mlflow
GHSA-j7qq-vr8c-xvw3
MLflow CrewAI autologging records LLM provider API keys in logged trace spans
Medium Also affects mlflow
GHSA-m65p-9j7q-6w33
MLflow vulnerable to arbitrary file read on unauthenticated servers via prompt model version source
High Also affects mlflow
GHSA-2wqp-q3c6-ccj5
MLflow: SSRF on unauthenticated MLflow servers via third-party scorer kwargs in the scorer invoke, register, and GenAI evaluate endpoints
Medium Also affects mlflow
GHSA-wqmh-qccw-pqwf
MLflow FileStore trace IDs allow path traversal and arbitrary file writes
High Also affects mlflow
GHSA-gqvg-gmmx-x4hm
MLFLOW_ALLOW_PICKLE_DESERIALIZATION=False safety control bypassed by mlflow.statsmodels flavor — RCE via crafted model artifact
High Also affects mlflow
GHSA-h7x2-h6g9-p789
MLflow AI Gateway permits SSRF through an unvalidated api_base
High Also affects mlflow
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor