Skip to main content

Llamaindex EUVDEUVD-2025-16964

| CVE-2025-1793 CRITICAL
SQL Injection (CWE-89)
2025-06-05 security@huntr.dev GHSA-v3c8-3pr6-gr7p
9.8
CVSS 3.0 · NVD
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

This vulnerability represents exceptionally high real-world risk. CVSS 9.8 with network attack vector (AV:N), low complexity (AC:L), no privileges required (PR:N), and no user interaction (UI:N) indicates trivial exploitation. The attack surface is broad—any web application using llama_index with vector store backends is potentially vulnerable. SQL injection is fully automatable and allows direct data exfiltration or manipulation without requiring additional exploitation steps. The combination of high CVSS, trivial attack requirements, and likely high EPSS score (SQL injection typically scores 0.97+) makes this a critical priority. Without KEV confirmation or POC disclosure data, the actual exploitation timeline is uncertain, but SQL injection is a well-understood attack class with extensive tooling available. Organizations should treat this as requiring emergency patching. The technical impact (CIA triad fully compromised) on confidentiality and integrity is maximum—attackers can read arbitrary data and modify database contents, potentially escalating to application compromise.

Exploit ScenarioDerived

An attacker discovers a web application using llama_index v0.12.21 for semantic search over sensitive user data (e.g., customer records, medical information). The application accepts free-text search queries from unauthenticated users. The attacker crafts a malicious search query such as: '; DROP TABLE users; -- or ' OR '1'='1 embedded in the search parameter. This input flows through the llama_index vector store integration to the underlying SQL database without parameterization. The attacker's SQL payload executes with the privileges of the database connection used by the application, allowing them to: (1) extract sensitive data using UNION-based or time-based SQL injection, (2) modify or delete records, (3) potentially escalate privileges within the database. The attack requires no authentication, no user interaction, and can be fully automated using standard SQL injection tools (e.g., sqlmap). A single request can compromise the entire database. No publicly disclosed POC is noted, but the CWE-89 attack class is well-researched with extensive tooling; exploitation is expected to be trivial once the vulnerability is publicly disclosed.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 14, 2026

Critical SQL injection vulnerability affecting run-llama/llama_index v0.12.21 and potentially other versions, present in multiple vector store integrations. Attackers can execute arbitrary SQL commands without authentication to read and write data, potentially compromising data belonging to other users in web applications leveraging this library. With a CVSS 9.8 severity score, network-accessible attack vector, and no authentication required, this vulnerability poses an immediate and severe risk to production deployments.

Affected VersionsENISA

run-llama/llama_index unspecified <0.12.28

Affected Packages

pypi llama-index fix: 0.12.28
euvd run_llama_llama_index_unspecified fix: 0.12.28

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in pypi, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Llama_index is a Python library for building LLM applications with vector store integrations for semantic search and data management. The vulnerability exists in SQL-based vector store adapters (likely PostgreSQL, MySQL, SQLite, or similar database backends) where user-supplied input is improperly sanitized before being concatenated into SQL queries. This is a classic CWE-89 (SQL Injection) vulnerability where dynamic SQL construction fails to use parameterized queries or prepared statements. The library's vector store integration layer accepts inputs (potentially from LLM prompts, user queries, or API parameters) that are passed directly to database drivers without proper escaping or parameterization, allowing attackers to inject malicious SQL syntax. Affected CPE likely includes: cpe:2.3:a:run-llama:llama_index:0.12.21:*:*:*:*:python:*:*

Know when Llamaindex gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Red Hat 9.1 HIGH

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
Patch released
Mar 14, 2026 - 17:53 nvd
Patch available
PoC Detected
Jul 30, 2025 - 21:29 vuln.today
Public exploit code
CVE Published
Jun 05, 2025 - 05:15 nvd
CRITICAL 9.8

DescriptionCVE.org

Multiple vector store integrations in run-llama/llama_index 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.

Executive ViewAI

Why It Matters

A critical SQL injection vulnerability in llama_index v0.12.21 allows attackers to read and write database data without authorization, potentially exposing customer information and enabling data manipulation. Organizations using this library in web applications face immediate risk of data breach and compliance violations.

Recommended Action

24 hours: Inventory all systems running llama_index v0.12.21 and assess exposure in internet-facing applications; immediately isolate affected systems if they handle sensitive data. 7 days: Apply the available vendor patch to all affected systems and validate the remediation in testing environments. 30 days: Conduct a security audit of data access logs to identify any unauthorized access during the vulnerability window and implement enhanced monitoring for SQL injection attempts.

Business Impact: Severe
Compensating Controls

Apply vendor patch. If immediate patching is not possible: implement Web Application Firewall (WAF) rules to block SQL injection patterns; restrict database user permissions to least-privilege access; disable vector store integrations if not actively required; implement database query logging and anomaly detection; segment affected applications from other critical systems.

Threat Intelligence Overview

EPSS Score
0.0%
Top 95% exploitable
Threat Intel
1
1 source
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity + public POC available
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Out-of-Cycle
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
Very High

Priority Score

69
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +49
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2024-11958 CRITICAL POC
9.8 Mar 20

A SQL injection vulnerability exists in the `duckdb_retriever` component of the run-llama/llama_index repository, specif

CVE-2024-12909 CRITICAL POC
9.8 Mar 20

A vulnerability in the FinanceChatLlamaPack of the run-llama/llama_index repository, versions up to v0.12.3, allows for

CVE-2025-1750 CRITICAL POC
9.8 Jun 02

SQL injection in llama_index DuckDB vector store v0.12.19. PoC and patch available.

CVE-2024-3271 CRITICAL POC
9.8 Apr 16

A command injection vulnerability exists in the run-llama/llama_index repository, specifically within the safe_eval func

CVE-2024-23751 CRITICAL POC
9.8 Jan 22

LlamaIndex (aka llama_index) through 0.9.34 allows SQL injection via the Text-to-SQL feature in NLSQLTableQueryEngine, S

CVE-2023-39662 CRITICAL POC
9.8 Aug 15

An issue in llama_index v.0.7.13 and before allows a remote attacker to execute arbitrary code via the `exec` parameter

CVE-2024-4181 HIGH POC
8.8 May 16

A command injection vulnerability exists in the RunGptLLM class of the llama_index library, version 0.9.47, used by the

CVE-2024-58339 HIGH POC
8.7 Jan 12

Denial-of-service in LlamaIndex (run-llama/llama_index) versions up to and including 0.12.2 lets remote unauthenticated

CVE-2024-14021 HIGH POC
8.4 Jan 12

Arbitrary code execution in LlamaIndex (run-llama/llama_index) versions up to and including 0.11.6 occurs when BGEM3Inde

CVE-2025-7707 HIGH POC
7.8 Oct 13

Local privilege escalation and denial of service in llama_index 0.12.33 arising from its default configuration of a worl

CVE-2025-3108 HIGH POC
7.5 Jul 06

A critical deserialization vulnerability exists in the run-llama/llama_index library's JsonPickleSerializer component, a

CVE-2025-1752 HIGH POC
7.5 May 10

A Denial of Service (DoS) vulnerability has been identified in the KnowledgeBaseWebReader class of the run-llama/llama_i

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy