CVE-2024-14021
Unsafe deserialization in LlamaIndex (<=0.11.6) enables code execution on load from disk.
Is CVE-2024-14021 being exploited?
Not confirmed. CVE-2024-14021 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.
How severe is CVE-2024-14021?
CVE-2024-14021 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-14021?
Yes. A fix has been recorded for CVE-2024-14021. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-14021 affect?
CVE-2024-14021 affects LlamaIndex (run-llama/llama_index) <= 0.11.6. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2024-14021?
Upgrade to fixed LlamaIndex version; avoid loading untrusted persists
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker with crafted persist_dir can trigger arbitrary code execution during index load via unsafe pickle.
Patch when possible
- affected<= 0.11.6
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.