# CVE-2025-1750: SQL Injection in run-llama/llama_index

> Attackers can exploit SQL injection in DuckDBVectorStore to read/write files and execute code on the server.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jun 2025
- **Updated:** 2 Jun 2025
- **Also known as:** GHSA-6mcc-q3mg-3qg6, PYSEC-2025-245, PYSEC-2026-4242

## What is CVE-2025-1750?

CVE-2025-1750 is a critical SQL injection vulnerability in run-llama/llama_index, published on 2 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An SQL injection vulnerability exists in the delete function of DuckDBVectorStore in run-llama/llama_index version v0.12.19. This vulnerability allows an attacker to manipulate the ref_doc_id parameter, enabling them to read and write arbitrary files on the server, potentially leading to remote code execution (RCE).

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

4 open source packages ship an affected version, including llama-index-vector-stores-duckdb and llama-index. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `llama-index-vector-stores-duckdb` | PyPI | From 0.12.19 | 0.12.21 |
| `llama-index-vector-stores-duckdb` | PyPI | From 0.12.19 | 0.12.21 |
| `llama-index-vector-stores-duckdb` | PyPI | From 0.12.19 | 0.12.21 |
| `llama-index` | PyPI | From 0.12.19 | 0.12.21 |

Products: Llamaindex Llamaindex.

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

Upgrade llama-index-vector-stores-duckdb to 0.12.21 or later.

## Is CVE-2025-1750 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1750 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-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)
- [CVE-2024-23751](https://insights.sbomify.com/CVE-2024-23751/): SQL injection in llama-index (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1750 is a critical SQL injection vulnerability in run-llama/llama_index, published on 2 Jun 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-1750 exists.

Affected packages and fixed versions:
- llama-index-vector-stores-duckdb (PyPI): affected from 0.12.19; fixed in 0.12.21
- llama-index-vector-stores-duckdb (PyPI): affected from 0.12.19; fixed in 0.12.21
- llama-index-vector-stores-duckdb (PyPI): affected from 0.12.19; fixed in 0.12.21
- llama-index (PyPI): affected from 0.12.19; fixed in 0.12.21

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-1750/ (Markdown: https://insights.sbomify.com/CVE-2025-1750/index.md)
```

## Sources

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

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