Arbitrary File Write via Archive Extraction (Zip Slip) Affecting mlflow-skinny package, versions [,3.9.0rc0)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-PYTHON-MLFLOWSKINNY-16698206
- published15 May 2026
- disclosed30 Mar 2026
- creditbilisheep
Introduced: 30 Mar 2026
CVE-2025-15036 (opens in a new tab)How to fix?
Upgrade mlflow-skinny to version 3.9.0rc0 or higher.
Overview
Affected versions of this package are vulnerable to Arbitrary File Write via Archive Extraction (Zip Slip) via the extract_archive_to_dir function. An attacker can overwrite arbitrary files or gain elevated privileges by supplying a crafted tar.gz file containing malicious paths during extraction. This may allow escape from the intended sandbox directory in multi-tenant or shared cluster environments.
Details
It is exploited using a specially crafted zip archive, that holds path traversal filenames. When exploited, a filename in a malicious archive is concatenated to the target extraction directory, which results in the final path ending up outside of the target folder. For instance, a zip may hold a file with a "../../file.exe" location and thus break out of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.
The following is an example of a zip archive with one benign file and one malicious file. Extracting the malicous file will result in traversing out of the target folder, ending up in /root/.ssh/ overwriting the authorized_keys file:
+2018-04-15 22:04:29 ..... 19 19 good.txt
+2018-04-15 22:04:42 ..... 20 20 ../../../../../../root/.ssh/authorized_keys