How severe is CVE-2025-3108?

CVE-2025-3108 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2025-3108 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (34th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-3108?

CVE-2025-3108 affects Llamaindex. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-3108?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-3108 have an EU (EUVD) identifier?

Yes. CVE-2025-3108 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-20156.

When was CVE-2025-3108 published?

CVE-2025-3108 was published on 2025-07-06 and last updated on 2026-06-17.

CVE-2025-3108

CVE-2025-3108 is a high-severity vulnerability in Llamaindex with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-1112.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 0% (34th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-20156
Weakness: CWE-1112
Affected product: Llamaindex
Published: 2025-07-06
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2025-3108?: 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.
How severe is CVE-2025-3108?: CVE-2025-3108 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-3108 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (34th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-3108?: CVE-2025-3108 affects Llamaindex. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-3108?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-3108 have an EU (EUVD) identifier?: Yes. CVE-2025-3108 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-20156.
When was CVE-2025-3108 published?: CVE-2025-3108 was published on 2025-07-06 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:llamaindex:llamaindex:*:*:*:*:*:*:*:*

More vulnerabilities in Llamaindex

CVE-2025-1793 — Critical (CVSS 9.8): Multiple vector store integrations in run-llama/llama_index version v0.12.21 have SQL injection vulnerabilities. These…
CVE-2025-1750 — Critical (CVSS 9.8): An SQL injection vulnerability exists in the delete function of DuckDBVectorStore in run-llama/llama_index version…
CVE-2024-12909 — Critical (CVSS 9.8): A vulnerability in the FinanceChatLlamaPack of the run-llama/llama_index repository, versions up to v0.12.3, allows for…
CVE-2024-11958 — Critical (CVSS 9.8): A SQL injection vulnerability exists in the `duckdb_retriever` component of the run-llama/llama_index repository,…
CVE-2024-3271 — Critical (CVSS 9.8): A command injection vulnerability exists in the run-llama/llama_index repository, specifically within the safe_eval…
CVE-2024-23751 — Critical (CVSS 9.8): LlamaIndex (aka llama_index) through 0.9.34 allows SQL injection via the Text-to-SQL feature in NLSQLTableQueryEngine,…

All CVEs affecting Llamaindex →

Other CWE-1112 vulnerabilities

CVE-2023-29241 — High (CVSS 8.1): Improper Information in Cybersecurity Guidebook in Bosch Building Integration System (BIS) 5.0 may lead to wrong…

Browse all CWE-1112 vulnerabilities →