CVE-2024-45201: LlamaIndex dynamic import execution vulnerability
llama-index-core, LlamaIndex
An insecure exec call in LlamaIndex before version 0.10.38 allows arbitrary code execution through crafted class names. A patch has been released by the vendor.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- CVSS
- 9.8
- EPSS
- 0.01 · top 55% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 22 Aug 2024
- last update
- 22 Aug 2024
- CVE ids
Timeline · 1
Sources · 1
Advisories and databases
- 2024-08-22CVE-2024-45201: LlamaIndex includes an exec call for `import {cls_name}`GitHub Advisory Database · github.com/advisories/GHSA-fxc2-8m62-m85x
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerability
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- mitre atlas
- no technique for these categories
- tags
- rcellamaindex
- dates
- happened 22 Aug 2024 · first reported 22 Aug 2024
- origin
- GitHub Advisory DatabaseVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 07:00Z · updated 2026-10-18 07:00Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# CVE-2024-45201: LlamaIndex dynamic import execution vulnerability
https://gcdradar.vercel.app/incidents/cve-2024-45201-llamaindex-dynamic-import-execution-vulnerabi · AIR-2024-0161 · closed 2024-08-22
- Lane: Patch now
- Severity: 2 (Disclosed vulnerability)
- Fix status: Fix status unknown
- First reported: 2024-08-22
- AI role: Attack on AI
- Products: llama-index-core, LlamaIndex
- CVE ids: CVE-2024-45201
- CVSS: 9.8
## Summary
An insecure exec call in LlamaIndex before version 0.10.38 allows arbitrary code execution through crafted class names. A patch has been released by the vendor.
## What to do
No action recorded; read the sources below and the vendor's advisory.
## Latest updates
- 2024-08-22: CVE-2024-45201: LlamaIndex includes an exec call for `import {cls_name}` (https://github.com/advisories/GHSA-fxc2-8m62-m85x)
## Sources
- 2024-08-22 GitHub Advisory Database: CVE-2024-45201: LlamaIndex includes an exec call for `import {cls_name}` https://github.com/advisories/GHSA-fxc2-8m62-m85x
Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.Related
- closed8.6LlamaIndex CVE-2025-5302: LlamaIndex Denial of Service in JSONReader
Patch now · Disclosed · since 26 Aug 2025 · CVE-2025-5302
AI - closed8.8LlamaIndex CVE-2024-4181: LlamaIndex RunGptLLM Command Injection
Patch now · Disclosed · since 16 May 2024 · CVE-2024-4181
AI - closed9.8LlamaIndex CVE-2024-3271: LlamaIndex command injection vulnerability
Patch now · Disclosed · since 16 Apr 2024 · CVE-2024-3271
AI - closed9.8LlamaIndex Llama Index Core Prompt Injection Leading to Code Execution
Patch now · Disclosed · since 10 Apr 2024 · CVE-2024-3098
AI - closed7.3LlamaIndex CVE-2025-7647: llama-index-core insecurely handles temporary files
Patch now · Disclosed · since 27 Sep 2025 · CVE-2025-7647
AI - closed6.5LlamaIndex CVE-2025-6211: LlamaIndex vulnerable to data loss via MD5 hash collisions
Patch now · Disclosed · since 10 Jul 2025 · CVE-2025-6211
AI