cve.bz

CVE-2025-3108 llamaindex llamaindex

7.5 highExploit referenceEPSS 0.5%Fix available

High (7.5) in llamaindex llamaindex. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in llama-index-core 0.12.41.

On this page
A critical deserialization vulnerability exists in the run-llama/llama_index library's JsonPickleSerializer component, affecting versions v0.12.27 through v0.12.40. This vulnerability allows remote code execution due to an insecure fallback to Python's pickle module. JsonPickleSerializer prioritizes deserialization using pickle.loads(), which can execute arbitrary code when processing untrusted data. Attackers can exploit this by crafting malicious payloads to achieve full system compromise. The root cause includes an insecure fallback mechanism, lack of validation or safeguards, misleading design, and violation of Python security guidelines.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 44th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2025-07-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-1112 Incomplete Documentation of Program Execution
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-3108 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-3108?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-3108?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-3108 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
run-llama/llama_indexbefore v0.12.41

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-m84c-4c34-28gfPyPIllama-index-core>=0.11.15 <0.12.410.12.41
PYSEC-2025-249PyPIllama-index>=0.12.27 <0.12.410.12.41
PYSEC-2026-1564PyPIllama-index-core>=0.11.15 <0.12.410.12.41

References

Check your stackJSON