run-llama llama_index up to 0.12.40 Pickle pickle.loads deserialization

Summaryinfo

A vulnerability has been found in run-llama llama_index up to 0.12.40 and classified as problematic. This affects the function pickle.loads of the component Pickle Module. The manipulation leads to deserialization. This vulnerability is traded as CVE-2025-3108. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in run-llama llama_index up to 0.12.40 and classified as problematic. This issue affects the function pickle.loads of the component Pickle Module. The manipulation with an unknown input leads to a deserialization vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at huntr.com. The identification of this vulnerability is CVE-2025-3108 since 04/02/2025. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 0.12.41 eliminates this vulnerability. Applying the patch 702e4340623092fac4cf2fe95eb9465034856da3 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-20156). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• run-llama

Name

• llama_index

Version

• 0.12.0
• 0.12.1
• 0.12.2
• 0.12.3
• 0.12.4
• 0.12.5
• 0.12.6
• 0.12.7
• 0.12.8
• 0.12.9
• 0.12.10
• 0.12.11
• 0.12.12
• 0.12.13
• 0.12.14
• 0.12.15
• 0.12.16
• 0.12.17
• 0.12.18
• 0.12.19
• 0.12.20
• 0.12.21
• 0.12.22
• 0.12.23
• 0.12.24
• 0.12.25
• 0.12.26
• 0.12.27
• 0.12.28
• 0.12.29
• 0.12.30
• 0.12.31
• 0.12.32
• 0.12.33
• 0.12.34
• 0.12.35
• 0.12.36
• 0.12.37
• 0.12.38
• 0.12.39
• 0.12.40

License

• open-source

Website

• Product: https://github.com/run-llama/llama_index/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion