Vulnerability in llama-index-core (CVE-2025-5472)
Summary
Vulnerability in llama-index-core (CVE-2025-5472). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.12.38 or later.
Original description
The description as published by the source.
The JSONReader in run-llama/llama_index versions 0.12.28 is vulnerable to a stack overflow due to uncontrolled recursive JSON parsing. This vulnerability allows attackers to trigger a Denial of Service (DoS) by submitting deeply nested JSON structures, leading to a RecursionError and crashing applications. The root cause is the unsafe recursive traversal design and lack of depth validation, which makes the JSONReader susceptible to stack overflow when processing deeply nested JSON. This impacts the availability of services, making them unreliable and disrupting workflows. The issue is resolved in version 0.12.38.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-5472 has been found in llama-index-core.
Risk of unauthorized operations or information disclosure.
What to do: upgrade llama-index-core to 0.12.38 or later.
If unsure, ask your IT team or search "llama-index-core CVE-2025-5472" on the vendor's site.
CVE-2025-5472 (llama-index-core) — CWE-674
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.12.38 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-674) exists in llama-index-core.
Check the vendor advisory for the affected versions of llama-index-core.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.12.38.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'llama-index-core' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'llama-index-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
llama-index-coreを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade llama-index-core to 0.12.38ステージング環境で 0.12.38 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web huntr.com