# CVE-2024-45201: PYSEC-2026-395 - LlamaIndex includes an exec call for `import {cls_name}`

Source: https://junglewise.ai/threats/cve-2024-45201-llamaindex-includes-an-exec-call-for-import-cls-name  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-29  
License: CC BY 4.0 with a link back

CVE-2024-45201 · Severity: low · CVSS 3.1 · Published 2026-06-29

LlamaIndex includes an exec call for `import {cls_name}`

Technologies: [llama-index (PyPI)](https://junglewise.ai/threats/technologies/llama-index), [llama-index-core (PyPI)](https://junglewise.ai/threats/technologies/llama-index-core). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2024-45201 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2024-45201 being exploited in the wild.

**How severe is CVE-2024-45201?** Low severity, with a CVSS score of 3.1, published 29 June 2026.

**Which products and versions are affected?** llama-index (PyPI) ECOSYSTEM:introduced=0,fixed=0.10.38; llama-index-core (PyPI) ECOSYSTEM:introduced=0,fixed=0.10.38.

**Is there a fix for CVE-2024-45201?** Yes. llama-index (PyPI): upgrade to 0.10.38 or later; llama-index-core (PyPI): upgrade to 0.10.38 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2024-45201?** Check whether you run llama-index (PyPI) or llama-index-core (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.10.38 or later

  ```sh
  pip install "llama-index>=0.10.38"
  ```

- llama-index-core (PyPI): upgrade to 0.10.38 or later

  ```sh
  pip install "llama-index-core>=0.10.38"
  ```


## Affected products

- llama-index (PyPI) ECOSYSTEM:introduced=0,fixed=0.10.38
- llama-index-core (PyPI) ECOSYSTEM:introduced=0,fixed=0.10.38

## Identifiers

- CVE-2024-45201
- GHSA-fxc2-8m62-m85x
- PYSEC-2024-192
- PYSEC-2026-395

## Related threats

- [PYSEC-2026-2606 - LlamaIndex vulnerable to data loss through hash collisions in its DocugamiReader class](https://junglewise.ai/threats/cve-2025-6211-llamaindex-vulnerable-to-data-loss-through-hash-collisions-in-its)
- [PYSEC-2026-1560 - llama-index-core vulnerable to Uncontrolled Resource Consumption](https://junglewise.ai/threats/cve-2025-6208-llama-index-core-vulnerable-to-uncontrolled-resource-consumption)
- [PYSEC-2026-1562 - llama-index-core insecurely handles temporary files](https://junglewise.ai/threats/cve-2025-7647-llama-index-core-insecurely-handles-temporary-files)
- [PYSEC-2026-1561 - LlamaIndex affected by a Denial of Service (DOS) in JSONReader](https://junglewise.ai/threats/cve-2025-5302-llamaindex-affected-by-a-denial-of-service-dos-in-jsonreader)
- [PYSEC-2026-1558 - LlamaIndex vulnerable to Path Traversal attack through its encode_image function](https://junglewise.ai/threats/cve-2025-6209-llamaindex-path-traversal-in-encode-image-function)