Live › vulnerability › CVE-2024-3098
Go to dashboardllama-index-core's exec_utils safe_eval function fails to block some code, so a prompt that reaches the pipeline can make the library run attacker-chosen code. The sources cite a proof of concept that writes a file on the host, and the flaw bypasses an earlier fix for CVE-2023-39662.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-27 17:32 UTC, 0h before NVD. All times on this page are UTC.
Applications that pass model output or user-supplied text into LlamaIndex features that call safe_eval, such as pandas query or similar code-evaluating paths, are exposed. Projects that use LlamaIndex only for retrieval over fixed documents, with no prompt-driven evaluation path, are less exposed, but the sources do not spell out which features reach safe_eval.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| llama-index-core | pypi | < 0.10.24 | 0.10.24 |
pip show llama-index-core and compare the version with 0.10.24llama-index-core below 0.10.24llama-index-core to 0.10.24 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
A vulnerability was identified in the exec_utils class of the llama_index package, specifically within the safe_eval function, allowing for prompt injection leading to arbitrary code execution. This issue arises due to insufficient validation of input, which can be exploited to bypass method restrictions and execute unauthorized code. The vulnerability is a bypass of the previously addressed CVE-2023-39662, demonstrated through a proof of concept that creates a file on the system by exploiting the flaw.
This page as .md · .json · in your agent: get_signal("CVE-2024-3098")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.