Approved changes feed: RSS · Atom

cpe:2.3:a:run-llama:llama_index:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorRun Llama (aa3ff240-aa06-5a4c-a0bb-edd7fd83fb4b)
ProductLlama Index (e370e323-0d4c-5a58-b984-244a2a8f03af)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2024-58339 vulnerable 2026-06-08 06:56:14.478538 LlamaIndex <= 0.12.2 VannaQueryEngine SQL Execution Allows Resource Exhaustion
LlamaIndex (run-llama/llama_index) versions up to and including 0.12.2 contain an uncontrolled resource consumption vulnerability in the VannaPack VannaQueryEngine implementation. The custom_query() logic generates SQL statements from a user-supplied prompt and executes them via vn.run_sql() without enforcing query execution limits In downstream deployments where untrusted users can supply prompts, an attacker can trigger expensive or unbounded SQL operations that exhaust CPU or memory resources, resulting in a denial-of-service condition. The vulnerable execution path occurs in llama_index/packs/vanna/base.py within custom_query().
Published: 2026-01-12T23:04:25.256Z
Updated: 2026-07-28T01:47:43.838Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-4181 vulnerable 2026-06-08 06:50:17.170536 Command Injection in run-llama/llama_index
HIGH (8.8)
A command injection vulnerability exists in the RunGptLLM class of the llama_index library, version 0.9.47, used by the RunGpt framework from JinaAI to connect to Language Learning Models (LLMs). The vulnerability arises from the improper use of the eval function, allowing a malicious or compromised LLM hosting provider to execute arbitrary commands on the client's machine. This issue was fixed in version 0.10.13. The exploitation of this vulnerability could lead to a hosting provider gaining full control over client machines.
Published: 2024-05-16T09:03:47.278Z
Updated: 2024-08-01T20:33:52.659Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-3271 vulnerable 2026-06-08 06:41:52.809207 Command Injection in run-llama/llama_index
CRITICAL (9.8)
A command injection vulnerability exists in the run-llama/llama_index repository, specifically within the safe_eval function. Attackers can bypass the intended security mechanism, which checks for the presence of underscores in code generated by LLM, to execute arbitrary code. This is achieved by crafting input that does not contain an underscore but still results in the execution of OS commands. The vulnerability allows for remote code execution (RCE) on the server hosting the application.
Published: 2024-04-16T00:00:15.108Z
Updated: 2024-08-01T20:05:08.348Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-3098 vulnerable 2026-06-08 06:41:52.409579 Prompt Injection leading to Arbitrary Code Execution in run-llama/llama_index
CRITICAL (9.8)
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.
Published: 2024-04-10T17:07:56.501Z
Updated: 2024-08-01T19:32:42.914Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-14021 vulnerable 2026-06-08 06:25:38.901706 LlamaIndex <= 0.11.6 BGEM3Index Unsafe Deserialization
LlamaIndex (run-llama/llama_index) versions up to and including 0.11.6 contain an unsafe deserialization vulnerability in BGEM3Index.load_from_disk() in llama_index/indices/managed/bge_m3/base.py. The function uses pickle.load() to deserialize multi_embed_store.pkl from a user-supplied persist_dir without validation. An attacker who can provide a crafted persist directory containing a malicious pickle file can trigger arbitrary code execution when the victim loads the index from disk.
Published: 2026-01-12T23:04:43.095Z
Updated: 2026-07-28T01:47:42.445Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.