Advisory record · GHSA-v3c8-3pr6-gr7p

llama_index vulnerable to SQL Injection

CVSS 9.8 CriticalCriticalEPSS 0.0072 · 54th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 5 Jun 2025, 06:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
llama-indexPyPI<0.12.280.12.28
Identifiers
GHSA-v3c8-3pr6-gr7p · CVE-2025-1793 · PYSEC-2026-394
Weakness (CWE)
CWE-89
Published
5 Jun 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The llama-index package, versions before 0.12.28, is affected by SQL injection in multiple vector store integrations. The source gives few details on the exact conditions, but it states that an attacker can read and write data using SQL, which may lead to access to other users' data depending on how the library is used in a web application. Upgrade llama-index to version 0.12.28 or later. No other workaround is listed.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.0 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CNA (@huntr_ai)
  • CISA KEV Not listed.
  • EPSS 0.0072, the 54th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:34 UTC First seen by agentprime
  2. 31 Oct 2026, 14:34 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.