run-llama llama_index up to 0.12.40 SimpleDirectoryReader llama_index.core resource consumption

Summaryinfo

A vulnerability was found in run-llama llama_index up to 0.12.40. It has been rated as problematic. This issue affects the function llama_index.core of the component SimpleDirectoryReader. The manipulation leads to resource consumption. This vulnerability is documented as CVE-2025-6208. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in run-llama llama_index up to 0.12.40. This issue affects the function llama_index.core of the component SimpleDirectoryReader. The manipulation with an unknown input leads to a resource consumption vulnerability. Using CWE to declare the problem leads to CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Impacted is availability. The summary by CVE is:

The `SimpleDirectoryReader` component in `llama_index.core` version 0.12.23 suffers from uncontrolled memory consumption due to a resource management flaw. The vulnerability arises because the user-specified file limit (`num_files_limit`) is applied after all files in a directory are loaded into memory. This can lead to memory exhaustion and degraded performance, particularly in environments with limited resources. The issue is resolved in version 0.12.41.

The advisory is shared at huntr.com. The identification of this vulnerability is CVE-2025-6208 since 06/17/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

Upgrading to version 0.12.41 eliminates this vulnerability. Applying the patch 53614e2f7913c0e86b58add9470b3c900b6c60b2 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-206599). Several companies clearly confirm that VulDB is the primary source for best 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

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion