Security Digest · Vulnerability record
CVE-2025-15036: MLFlow path traversal vulnerability
A path traversal vulnerability exists in the extractarchivetodir function within the mlflow/pyfunc/dbconnectartifactcache.py file of the mlflow/mlflow repository.
CVSS 9.6 Critical EPSS 0.6% · p47
Should you act?
Critical and remotely reachable
No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 0.6%, percentile 47: FIRST’s model estimates a 0.6% chance of exploitation activity in the next 30 days, higher than 47% of all scored CVEs (low). EPSS is a probability, not a verdict.
- Needs a user to click or open something. Phishing makes that realistic, but it is not wormable.
- Only applies if your dependency tree includes
mlflow(PyPI) < 3.9.0rc0, fixed in 3.9.0rc0. Check your lockfile, including transitive dependencies.
What it is
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.
From the GitHub advisory
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.
Weakness type: CWE-29, CWE-22.
Product: mlflow (PyPI) · Assigned by: @huntr_ai · Published: 2026-03-30
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| PyPI | mlflow | < 3.9.0rc0 | 3.9.0rc0 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| mlflow | mlflow/mlflow | unspecified < 3.9.0 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| @huntr_ai | 3.0 | 9.6 Critical | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H |
| redhat-SADP | 3.1 | 9.6 Critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 9.6 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: none (no login)
- User interaction: required (a user must click/open something)
- Scope: changed (can affect other components)
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc, automatable no, technical impact total.
- FIRST EPSS (model of 2026-10-21): 0.58% probability of exploitation activity in the next 30 days; percentile 47.
Timeline
- — CVE record published by @huntr_ai
- — GitHub-reviewed advisory GHSA-vhcx-3pq2-4fvc published (critical)
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-vhcx-3pq2-4fvc github.com
- CVE.org record CVE-2025-15036 cve.org
- NVD entry CVE-2025-15036 nvd.nist.gov
Other references from the CVE record and advisory
- huntr.com huntr.com
- github.com github.com
- access.redhat.com access.redhat.com
- RHBZ#2452925 bugzilla.redhat.com
- security.access.redhat.com security.access.redhat.com