Is CVE-2025-1793 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-1793 being exploited in the wild.

How severe is CVE-2025-1793?

Critical severity, with a CVSS score of 9.8, published 5 June 2025.

Which products and versions are affected?

llama-index (PyPI) < 0.12.28, ECOSYSTEM:introduced=0,fixed=0.12.28.

Is there a fix for CVE-2025-1793?

Yes. llama-index (PyPI): upgrade to 0.12.28 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-1793 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2025-1793?

Check whether you run Llamaindex or llama-index (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-1793: run-llama llama-index SQL injection in vector store integrations

Q: Which products and versions are affected?

llama-index (PyPI) < 0.12.28, ECOSYSTEM:introduced=0,fixed=0.12.28.

Q: Is there a fix for CVE-2025-1793?

Yes. llama-index (PyPI): upgrade to 0.12.28 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2025-1793 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2025-1793?

Check whether you run Llamaindex or llama-index (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-1793 · Severity: critical · CVSS 9.8 · Published 2025-06-05

LlamaIndex, a popular framework for connecting custom data to Large Language Models (LLMs), contains a vulnerability in how it handles database queries. An attacker could exploit this to read, modify, or delete sensitive information stored in the application's database. This could lead to unauthorized access to user data or a complete compromise of the data used by the AI application.

Technologies: Llamaindex, llama-index (PyPI). Vendors: Llamaindex, PyPI.

Quick answers

Is CVE-2025-1793 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-1793 being exploited in the wild.
How severe is CVE-2025-1793?: Critical severity, with a CVSS score of 9.8, published 5 June 2025.
Which products and versions are affected?: llama-index (PyPI) < 0.12.28, ECOSYSTEM:introduced=0,fixed=0.12.28.
Is there a fix for CVE-2025-1793?: Yes. llama-index (PyPI): upgrade to 0.12.28 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-1793 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-1793?: Check whether you run Llamaindex or llama-index (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

llama-index (PyPI): upgrade to 0.12.28 or later
```
pip install "llama-index>=0.12.28"
```

Technical details

Multiple vector store integrations in llama-index (before version 0.12.28) fail to properly neutralize special elements used in SQL commands, leading to a CWE-89 SQL Injection vulnerability. The root cause is the construction of SQL queries using externally-influenced input without sufficient sanitization or parameterized queries. A remote, unauthenticated attacker can exploit this by sending crafted input to an application using the library, enabling them to execute arbitrary SQL commands. This allows for unauthorized reading and writing of data within the underlying database. The vulnerability was addressed in version 0.12.28.

Affected products

run-llama llama-index < 0.12.28

Identifiers

CVE-2025-1793
GHSA-v3c8-3pr6-gr7p
PYSEC-2026-394

Timeline

2025-06-05: advisory: GitHub Advisory published
2025-06-05: disclosed: NVD publication date
2025-06-06: other: GitHub Advisory reviewed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.