A vulnerability marked as critical has been reported in mlflow . The affected element is an unknown function of the component tar Handler . Performing a manipulation results in path traversal. This vulnerability is identified as CVE-2025-15031 . The attack can only be performed from the local network. There is not any exploit available. It is suggested to upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-351622 · CVE-2025-15031 · GCVE-0-2025-15031
MLFLOW TAR PATH TRAVERSAL
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
7.0 $0-$5k 0.55+
Summaryinfo
A vulnerability described as critical has been identified in mlflow. The impacted element is an unknown function of the component tar Handler. Executing a manipulation can lead to path traversal. This vulnerability is tracked as CVE-2025-15031. The attack is only possible within the local network. No exploit exists. Upgrading the affected component is recommended.
Detailsinfo
A vulnerability classified as critical was found in mlflow (unknown version). This vulnerability affects an unknown code block of the component tar Handler. The manipulation with an unknown input leads to a path traversal vulnerability. The CWE definition for the vulnerability is CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
A vulnerability in MLflow's pyfunc extraction process allows for arbitrary file writes due to improper handling of tar archive entries. Specifically, the use of `tarfile.extractall` without path validation enables crafted tar.gz files containing `..` or absolute paths to escape the intended extraction directory. This issue affects the latest version of MLflow and poses a high/critical risk in scenarios involving multi-tenant environments or ingestion of untrusted artifacts, as it can lead to arbitrary file overwrites and potential remote code execution.
The advisory is available at huntr.com. This vulnerability was named CVE-2025-15031 since 12/22/2025. The exploitation appears to be easy. Access to the local network is required for this attack. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1006 by the MITRE ATT&CK project.
Upgrading eliminates this vulnerability.
Productinfo
Name
mlflow
CPE 2.3info
🔒
CPE 2.2info
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 7.2
VulDB Meta Temp Score: 7.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.1
CNA Vector (@huntr_ai): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Path traversal
CWE: CWE-22
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Timelineinfo
12/22/2025 CVE reserved
03/18/2026 +86 days Advisory disclosed
03/18/2026 +0 days VulDB entry created
03/18/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: huntr.com
Status: Confirmed
CVE: CVE-2025-15031 (🔒)
GCVE (CVE): GCVE-0-2025-15031
GCVE (VulDB): GCVE-100-351622
Entryinfo
Created: 03/18/2026 23:57
Changes: 03/18/2026 23:57 (61)
Complete: 🔍
Cache ID: 99:9AB:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸