Security Digest · Vulnerability record
CVE-2025-1793: llama_index vulnerable to SQL Injection
Multiple vector store integrations in run-llama/llamaindex version v0.12.21 have SQL injection vulnerabilities.
CVSS 9.8 Critical EPSS 0.7% · p51
Should you act?
Critical and remotely reachable
No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 0.7%, percentile 51: FIRST’s model estimates a 0.7% chance of exploitation activity in the next 30 days, higher than 51% 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(PyPI) < 0.12.28, fixed in 0.12.28. Check your lockfile, including transitive dependencies.
What it is
Multiple vector store integrations in run-llama/llamaindex version v0.12.21 have SQL injection vulnerabilities. These vulnerabilities allow an attacker to read and write data using SQL, potentially leading to unauthorized access to data of other users depending on the usage of the llama-index library in a web application.
From the GitHub advisory
Multiple vector store integrations in run-llama/llamaindex version v0.12.21 have SQL injection vulnerabilities. These vulnerabilities allow an attacker to read and write data using SQL, potentially leading to unauthorized access to data of other users depending on the usage of the llama-index library in a web application.
Weakness type: CWE-89.
Product: llama-index (PyPI) · Assigned by: @huntr_ai · Published: 2025-06-05
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| PyPI | llama-index | < 0.12.28 | 0.12.28 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| run-llama | run-llama/llama_index | unspecified < 0.12.28 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| @huntr_ai | 3.0 | 9.8 Critical | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: none (no login)
- User interaction: none
- Scope: unchanged
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- 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.66% probability of exploitation activity in the next 30 days; percentile 51.
Timeline
- — CVE record last updated
- — CVE record published by @huntr_ai
- — GitHub-reviewed advisory GHSA-v3c8-3pr6-gr7p published (critical)
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-v3c8-3pr6-gr7p github.com
- CVE.org record CVE-2025-1793 cve.org
- NVD entry CVE-2025-1793 nvd.nist.gov
Other references from the CVE record and advisory
- huntr.com huntr.com
- github.com github.com
- github.com github.com
- github.com github.com
- pypi.org pypi.org