CVE-2025-15036
Lfprojects Mlflow path traversal
- Published30 Mar 2026
Description
A path traversal vulnerability exists in the `extract_archive_to_dir` function within the `mlflow/pyfunc/dbconnect_artifact_cache.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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/security/cve/CVE-2025-15036
- https://bugzilla.redhat.com/show_bug.cgi?id=2452925
- https://github.com/mlflow/mlflow/commit/3bf6d81ac4d38654c8ff012dbd0c3e9f17e7e346
- https://huntr.com/bounties/36c314cf-fd6e-4fb0-b9b0-1b47bcdf0eb0
- https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-15036.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-15036 being actively exploited?
CVE-2025-15036 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.58%.
How severe is CVE-2025-15036?
CVE-2025-15036 has a CVSS 3.1 base score of 10.0, rated critical. EPSS estimates a 0.58% probability of exploitation.
Which products are affected by CVE-2025-15036?
Affected products include Lfprojects Mlflow.
How do I fix CVE-2025-15036?
Upgrade affected software to a fixed version, for example Lfprojects Mlflow 3.9.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-15036 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.