CVE-2025-15036: mlflow/mlflow · Path Traversal: '\..\filename
Affects mlflow/mlflowSource CVE Database V5
Not known to be exploited · CVSS 9.6 Critical : upgrade to 3.7.0 as a priority.
Data as of 30 Oct 2026, 11:52 UTC
Contested
Critical score, yet low EPSS after six months- EPSS
- 0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.7.0
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 30 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade mlflow to 3.7.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| mlflowmlflow/mlflow | Affected
| Fixed in– |
PyPImlflowpkg:pypi/mlflowOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in mlflow version 3.7.0 and later. Users should upgrade to version 3.7.0 or newer to remediate this vulnerability. The vendor advisory from Red Hat confirms the issue and provides guidance on patching. Until upgrading, avoid processing untrusted tar.gz files with the vulnerable function to mitigate risk.
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.
References
- huntr.com/bounties/36c314cf-fd6e-4fb0-b9b0-1b47bcdf0eb0 (opens in a new tab)
- github.com/mlflow/mlflow/commit/3bf6d81ac4d38654c8ff012dbd0c3e9f17e7e346 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-15036 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2452925 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-15036.json (opens in a new tab)