Arbitrary File Write via Archive Extraction (Zip Slip) Affecting llama-index package, versions [,0.12.41)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
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-LLAMAINDEX-10648999
- published8 Jul 2025
- disclosed7 Jul 2025
- creditManan Patel
Introduced: 7 Jul 2025
NewCVE-2025-6209 (opens in a new tab)How to fix?
Upgrade llama-index to version 0.12.41 or higher.
Overview
llama-index is an Interface between LLMs and your data
Affected versions of this package are vulnerable to Arbitrary File Write via Archive Extraction (Zip Slip) via the encode_image function. An attacker can access arbitrary files on the server by supplying crafted image_path values containing path traversal sequences.
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