Quick answers
- Is CVE-2024-14021 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-14021 being exploited in the wild.
- How severe is CVE-2024-14021?
- High severity, with a CVSS score of 7.8, published 12 January 2026.
- Which products and versions are affected?
- Llamaindex <= 0.11.6; llama-index (PyPI) ECOSYSTEM:introduced=0,fixed=0.11.7.
- Is there a fix for CVE-2024-14021?
- Yes. llama-index (PyPI): upgrade to 0.11.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2024-14021 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2024-14021?
- Check whether you run Llamaindex or llama-index (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- llama-index (PyPI): upgrade to 0.11.7 or later
pip install "llama-index>=0.11.7"
Technical details
An unsafe deserialization vulnerability exists in LlamaIndex (run-llama/llama_index) versions up to and including 0.11.6 within the BGEM3Index.load_from_disk() function. The root cause is the use of the Python 'pickle' module to load the 'multi_embed_store.pkl' file from a user-provided directory without any validation. Because 'pickle' is inherently insecure for untrusted data, an attacker can craft a malicious pickle file that executes arbitrary commands when deserialized. Exploitation requires a victim to point the library to a directory controlled by the attacker; this is classified as a local attack vector with required user interaction.
Affected products
- run-llama LlamaIndex <= 0.11.6
Identifiers
- CVE-2024-14021
- PYSEC-2026-85
Timeline
- 2026-01-12: disclosed: Initial disclosure via VulnCheck and NVD
- 2026-01-12: advisory