# CVE-2025-6211: MD5 Hash Collision in run-llama/llama_index

> Attackers can cause data loss and AI hallucinations in llama_index by exploiting MD5 hash collisions in document chunking.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jul 2025
- **Updated:** 10 Jul 2025
- **Also known as:** GHSA-5hq9-5r78-2gjh, PYSEC-2026-1566, PYSEC-2026-2606

## What is CVE-2025-6211?

CVE-2025-6211 is a medium-severity vulnerability in run-llama/llama_index, published on 10 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-440 (Expected Behavior Violation)

## Which versions are affected by CVE-2025-6211?

6 open source packages ship an affected version, including llama-index and llama-index-readers-docugami. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `llama-index` | PyPI | All versions | 0.12.41 |
| `llama-index` | PyPI | All versions | 0.12.41 |
| `llama-index` | PyPI | All versions | 0.12.41 |
| `llama-index-readers-docugami` | PyPI | All versions | 0.3.1 |
| `llama-index-readers-docugami` | PyPI | All versions | 0.3.1 |
| `llama-index-readers-docugami` | PyPI | All versions | 0.3.1 |

Products: Llamaindex Llamaindex.

## How do I fix CVE-2025-6211?

Upgrade llama-index to 0.12.41 or later.

## Is CVE-2025-6211 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6211 exists.

## Other vulnerabilities in run-llama/llama_index

- [CVE-2024-12909](https://insights.sbomify.com/CVE-2024-12909/): SQL Injection to RCE in run-llama/llama_index (critical 10.0)
- [CVE-2025-1793](https://insights.sbomify.com/CVE-2025-1793/): SQL Injection in run-llama/llama_index (critical 9.8)
- [CVE-2025-1750](https://insights.sbomify.com/CVE-2025-1750/): SQL Injection in run-llama/llama_index (critical 9.8)
- [CVE-2024-11958](https://insights.sbomify.com/CVE-2024-11958/): SQL Injection in run-llama/llama_index (critical 9.8)
- [CVE-2024-3271](https://insights.sbomify.com/CVE-2024-3271/): Command Injection in run-llama/llama_index (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6211 and fix it if it is affected.

What it is: CVE-2025-6211 is a medium-severity vulnerability in run-llama/llama_index, published on 10 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6211 exists.

Affected packages and fixed versions:
- llama-index (PyPI): affected all versions; fixed in 0.12.41
- llama-index (PyPI): affected all versions; fixed in 0.12.41
- llama-index (PyPI): affected all versions; fixed in 0.12.41
- llama-index-readers-docugami (PyPI): affected all versions; fixed in 0.3.1
- llama-index-readers-docugami (PyPI): affected all versions; fixed in 0.3.1
- llama-index-readers-docugami (PyPI): affected all versions; fixed in 0.3.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-6211/ (Markdown: https://insights.sbomify.com/CVE-2025-6211/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-6211
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-6211
- OSV: https://osv.dev/vulnerability/CVE-2025-6211

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-6211/
Summaries are generated and may contain mistakes; the official description above is the record.