---
title: "CVE-2025-1750: LlamaIndex DuckDBVectorStore vulnerable to SQL injection through ref_doc_id"
url: https://erroneo.us/security/cve/CVE-2025-1750/
description: "CVE-2025-1750 (llama-index-vector-stores-duckdb (PyPI)): An SQL injection vulnerability exists in the delete function of DuckDBVectorStore in…"
type: vulnerability-record
section: "Security Digest"
date_published: 2025-06-02
date_modified: 2026-10-02
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2025-1750"
kev: false
cvss: 9.8
epss: 0.00817
license: All rights reserved. Quote with attribution and a link.
---

# CVE-2025-1750: LlamaIndex DuckDBVectorStore vulnerable to SQL injection through ref_doc_id

**Signal:** Critical and remotely reachable. No known exploitation yet, but it is network-reachable without credentials. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- Not in CISA KEV , but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 0.8% , percentile 57: FIRST’s model estimates a 0.8% chance of exploitation activity in the next 30 days, higher than 57% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes llama-index-vector-stores-duckdb (PyPI) >= 0.12.19, < 0.12.21, fixed in 0.12.21 . Check your lockfile, including transitive dependencies.

## What it is

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

## Affected packages

- PyPI `llama-index-vector-stores-duckdb` >= 0.12.19, < 0.12.21 → fixed: 0.12.21

## Affected products (CVE record)

- run-llama run-llama/llama_index: unspecified < 0.3.1

## Severity

- @huntr_ai CVSS 3.0: 9.8 `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`
- GitHub CVSS 3.1: 9.8 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`

## Exploitation

- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc , automatable yes , technical impact total .
- FIRST EPSS (model of 2026-10-21): 0.82% probability of exploitation activity in the next 30 days; percentile 57.

## Sources

- [GitHub Advisory GHSA-6mcc-q3mg-3qg6](https://github.com/advisories/GHSA-6mcc-q3mg-3qg6)
- [CVE.org record CVE-2025-1750](https://www.cve.org/CVERecord?id=CVE-2025-1750)
- [NVD entry CVE-2025-1750](https://nvd.nist.gov/vuln/detail/CVE-2025-1750)
- [huntr.com](https://huntr.com/bounties/e1302233-9180-4269-9047-1526247d2cd8)
- [github.com](https://github.com/run-llama/llama_index/commit/369a2942df2efcf6b74461c45d20a0af1fbe4ae2)
- [github.com](https://github.com/pypa/advisory-database/tree/main/vulns/llama-index/PYSEC-2025-245.yaml)
- [github.com](https://github.com/run-llama/llama_index/releases/tag/v0.12.21)

---
Source page: https://erroneo.us/security/cve/CVE-2025-1750/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt