CVE-2024-14021: LlamaIndex unsafe deserialization vulnerability
LlamaIndex
LlamaIndex contains an unsafe deserialization vulnerability via pickle loading in BGEM3Index.load_from_disk. Attackers can achieve arbitrary code execution using crafted index directories.
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
- 8.4
- EPSS
- <0.01 · top 73% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 12 Jan 2026
- last update
- 12 Jan 2026
- CVE ids
Timeline · 1
Sources · 1
Advisories and databases
- 2026-01-12CVE-2024-14021: LlamaIndex (run-llama/llama_index) versions up to and including 0.11.6 contain an unsafe deserialization vulnerability in…NVD · nvd.nist.gov/vuln/detail/CVE-2024-14021
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
- deserialization
- dates
- happened 12 Jan 2026 · first reported 12 Jan 2026
- origin
- NVDVulnerability 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 10:04Z · updated 2026-10-18 10:04Z
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-14021: LlamaIndex unsafe deserialization vulnerability https://gcdradar.vercel.app/incidents/cve-2024-14021-llamaindex-unsafe-deserialization-vulnerabili · AIR-2026-0941 · closed 2026-01-12 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2026-01-12 - AI role: Attack on AI - Products: LlamaIndex - CVE ids: CVE-2024-14021 - CVSS: 8.4 ## Summary LlamaIndex contains an unsafe deserialization vulnerability via pickle loading in BGEM3Index.load_from_disk. Attackers can achieve arbitrary code execution using crafted index directories. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-01-12: CVE-2024-14021: LlamaIndex (run-llama/llama_index) versions up to and including 0.11.6 contain an unsafe deserialization vulnerability in… (https://nvd.nist.gov/vuln/detail/CVE-2024-14021) ## Sources - 2026-01-12 NVD: CVE-2024-14021: LlamaIndex (run-llama/llama_index) versions up to and including 0.11.6 contain an unsafe deserialization vulnerability in… https://nvd.nist.gov/vuln/detail/CVE-2024-14021 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed8.7LlamaIndex CVE-2024-58339: LlamaIndex uncontrolled resource consumption in VannaQueryEngine
Patch now · Disclosed · since 12 Jan 2026 · CVE-2024-58339
AI - closedLangChain family RCE Vulnerabilities in LLM-Integrated Applications via Prompt Injection
Research · since 27 Feb 2025
AI - closed8.6LlamaIndex CVE-2025-5302: LlamaIndex Denial of Service in JSONReader
Patch now · Disclosed · since 26 Aug 2025 · CVE-2025-5302
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 - closed7.5LlamaIndex CVE-2025-6209: LlamaIndex path traversal vulnerability in encode_image
Patch now · Disclosed · since 7 Jul 2025 · CVE-2025-6209
AI - closed9.8LlamaIndex CVE-2025-1793: LlamaIndex SQL Injection Vulnerability
Patch now · Disclosed · since 5 Jun 2025 · CVE-2025-1793
AI