run-llama llama_index up to 0.3.0 MD5 Hash DocugamiReader expected behavior violation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in run-llama llama_index up to 0.3.0. This vulnerability affects the function DocugamiReader of the component MD5 Hash Handler. The manipulation leads to expected behavior violation.
This vulnerability is traded as CVE-2025-6211. It is possible to initiate the attack remotely. There is no exploit available.
You should upgrade the affected component.
Details
A vulnerability was found in run-llama llama_index up to 0.3.0. It has been rated as critical. This issue affects the function DocugamiReader of the component MD5 Hash Handler. The manipulation with an unknown input leads to a expected behavior violation vulnerability. Using CWE to declare the problem leads to CWE-440. A feature, API, or function does not perform according to its specification. Impacted is integrity, and availability. The summary by CVE is:
A vulnerability in the DocugamiReader class of the run-llama/llama_index repository, up to version 0.12.28, involves the use of MD5 hashing to generate IDs for document chunks. This approach leads to hash collisions when structurally distinct chunks contain identical text, resulting in one chunk overwriting another. This can cause loss of semantically or legally important document content, breakage of parent-child chunk hierarchies, and inaccurate or hallucinated responses in AI outputs. The issue is resolved in version 0.3.1.
The advisory is shared at huntr.com. The identification of this vulnerability is CVE-2025-6211 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.
Upgrading to version 0.3.1 eliminates this vulnerability. Applying the patch 29b2e07e64ed7d302b1cc058185560b28eaa1352 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-20993). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (@huntr_ai): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Expected behavior violationCWE: CWE-440 / CWE-436
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: llama_index 0.3.1
Patch: 29b2e07e64ed7d302b1cc058185560b28eaa1352
Timeline
06/17/2025 CVE reserved07/10/2025 Advisory disclosed
07/10/2025 VulDB entry created
07/31/2025 VulDB entry last update
Sources
Product: github.comAdvisory: huntr.com
Status: Confirmed
CVE: CVE-2025-6211 (🔒)
GCVE (CVE): GCVE-0-2025-6211
GCVE (VulDB): GCVE-100-315989
EUVD: 🔒
Entry
Created: 07/10/2025 16:21Updated: 07/31/2025 00:38
Changes: 07/10/2025 16:21 (66), 07/10/2025 16:38 (1), 07/31/2025 00:38 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.