Skip to content
Submit incident
AII-1001-85797
ConfirmedA court, a regulator or the organization itself has stated the core facts, or the record cites a court or regulator source.

Path traversal vulnerability in MLflow (CVE-2024-8859)

A path traversal vulnerability in MLflow's model version source validation was fixed by improving checks to reject relative path sequences like \"..\" that could bypass security controls.

20 March 2025 Β· MLflow Β· Security and cyberattacks
20 March 2025
AII-1001-857973 sources ↓
Quick facts
Organization
MLflow (subject)
Category
Security and cyberattacks
Source
github.com
Date
20 March 2025
Drafted by
Raidu Incident Detection

What happened

A path traversal vulnerability was identified in MLflow's validation logic for model version sources. The vulnerability allowed attackers to bypass source validation checks using relative path sequences.

Governance controls

MLflow improved the `_validate_non_local_source_contains_relative_paths` function to reject sources containing relative path traversal sequences. The fix added a check to reject any source containing ".." path components in addition to existing null byte validation.

Classification

Organization
MLflow (subject)
Category
Security and cyberattacks
Industry
IT infrastructure and hosting
Harm status
Potential harm
Intent
Unintentional
Timing
Unknown
AI systems
MLflow

Sources and evidence

This record was researched and written by the Index, based on the following original reporting.

github.com
https://github.com/mlflow/mlflow/commit/7791b8cdd595f21b5f179c7b17e4b5eb5cbbe654
huntr.com
https://huntr.com/bounties/2259b88b-a0c6-4c7c-b434-6aacf6056dcb
cve.org
NVD entry