Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
CRITICAL severity

GHSA-fxc2-8m62-m85x — llama-index-core

CRITICALFix: run-llama/llama_index#13523

GHSA-fxc2-8m62-m85x is a critical-severity (CVSS 9.8) Code Injection vulnerability in llama-index-core. A fix is available for llama-index-core — see the affected versions and patch details below.

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

Also known asCVE-2024-45201PYSEC-2024-192PYSEC-2026-395
Published
Aug 22, 2024
Updated
Jun 29, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-fxc2-8m62-m85x.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-fxc2-8m62-m85x by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
🐍llama-index-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

An issue was discovered in llama_index before 0.10.38. download/integration.py includes an exec call for import {cls_name}.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIllama-index-coreall versions0.10.38pip install --upgrade 'llama-index-core==0.10.38'

Affected Products

1 product · 1 configurations
Application
llamaindexllamaindex
< 0.10.38
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for llama-index-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update llama-index-core to 0.10.38 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fxc2-8m62-m85x is resolved across your whole dependency graph.

  3. Workarounds

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

An issue was discovered in llama_index before 0.10.38. `download/integration.py` includes an exec call for `import {cls_name}`.
O3 Security · Impact-Aware SCA

Is GHSA-fxc2-8m62-m85x in your dependencies?

Find it across PyPI, including transitive dependencies.

GHSA-fxc2-8m62-m85x: llama-index-core | O3 Security