CVE-2025-15036: Path Traversal Vulnerability in mlflow/mlflow
A path traversal vulnerability exists in the extractarchivetodir function within the mlflow/pyfunc/dbconnectartifactcache.py file of the mlflow/mlflow repository. This vulnerability, present in versions before v3.7.0, arises due to the lack of validation of tar member paths during extraction. An attacker with control over the tar.gz file can exploit this issue to overwrite arbitrary files or gain elevated privileges, potentially escaping the sandbox directory in multi-tenant or shared cluster environments.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
mlflow/mlflowto a version that resolves this vulnerability.Fixed in v3.7.0 - Configuration
Update the `extract_archive_to_dir` extraction logic to validate each tar member path before writing, rejecting any path traversal attempts that would result in writing outside the intended sandbox directory.
mlflow/pyfunc/dbconnect_artifact_cache.py (extract_archive_to_dir) tar member path validation during extraction = validate and reject tar member paths that would escape the sandbox extraction directory (e.g., ../ or absolute paths)
Event History
Frequently Asked Questions
What is the severity of CVE-2025-15036?
CVE-2025-15036 is considered a high severity vulnerability due to the potential for unauthorized access to sensitive files.
How do I fix CVE-2025-15036?
To fix CVE-2025-15036, upgrade the mlflow package to version 3.7.0 or later.
What versions are affected by CVE-2025-15036?
CVE-2025-15036 affects all versions of mlflow prior to 3.7.0.
What type of vulnerability is CVE-2025-15036?
CVE-2025-15036 is a path traversal vulnerability that can allow attackers to access unauthorized files.
Is there a workaround for CVE-2025-15036?
There are no recommended workarounds for CVE-2025-15036; upgrading to the fixed version is advised.