VulnerabilityPublished 6 Jul 2025

CVE-2025-3108: run-llama/llama_index · Incomplete Documentation of Program Execution

Affects run-llama/llama_indexSource CVE Database V5

Not known to be exploited · CVSS 5.0 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.0 base score

5.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
run-llama run-llama/llama_index	Affected >=0.12.27 <=0.12.40	Fixed in–

AI-suggested

Immediate mitigation involves auditing all use cases of the run-llama/llama_index library, particularly where JsonPickleSerializer is employed for deserialization.
Avoid deserializing untrusted or unauthenticated data using this component.
Implement strict input validation and sandboxing around deserialization processes to limit potential damage.
Where possible, replace or configure JsonPickleSerializer to use safer serialization formats that do not rely on pickle, such as JSON without fallback to pickle.
Monitor for unusual application behavior or unexpected code execution patterns that could indicate exploitation attempts.
Engage with the vendor or open-source maintainers to obtain patches or updates addressing this vulnerability as soon as they become available.
Employ network-level controls to restrict inbound traffic to services using the vulnerable library, reducing exposure to remote attacks.
Educate developers and security teams about the risks of insecure deserialization and enforce secure coding practices.
Consider application-layer firewalls or runtime application self-protection (RASP) solutions to detect and block malicious payloads targeting deserialization flaws.

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.

Impact

For European organizations, the impact of CVE-2025-3108 can be substantial, particularly for those leveraging the run-llama/llama_index library in their software stacks or AI-related applications. Given the vulnerability enables remote code execution, attackers could gain unauthorized control over affected systems, leading to data breaches, intellectual property theft, or disruption of critical services. This is especially concerning for sectors such as finance, healthcare, government, and critical infrastructure, where confidentiality and integrity are paramount. The medium CVSS score somewhat underrepresents the risk because exploitation requires user interaction and high attack complexity; however, in environments where deserialization of untrusted data occurs automatically or with minimal oversight, the threat escalates. Additionally, the lack of patches and public exploits means organizations must proactively mitigate risks. The vulnerability could also undermine trust in AI and data processing applications, impacting compliance with GDPR and other data protection regulations if personal data is compromised. Overall, the threat could lead to operational downtime, regulatory penalties, and reputational damage for European entities.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Jul 2025, 23:09 UTC

WeaknessesCWE-1112

Technical details

References

Community reviews

Related threats