Security Digest · Vulnerability record
CVE-2024-12909: llama-index-packs-finchat SQL Injection vulnerability
A vulnerability in the FinanceChatLlamaPack of the run-llama/llamaindex repository, versions up to v0.12.3, allows for SQL injection in the runsqlquery function of the databaseagent.
CVSS 10.0 Critical EPSS 1.4% · p73
Should you act?
Critical and remotely reachable
No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 1.4%, percentile 73: FIRST’s model estimates a 1.4% chance of exploitation activity in the next 30 days, higher than 73% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes
llama-index-packs-finchat(PyPI) <= 0.3.0, no fixed version listed. Check your lockfile, including transitive dependencies.
What it is
A vulnerability in the FinanceChatLlamaPack of the run-llama/llamaindex repository, versions up to v0.12.3, allows for SQL injection in the runsqlquery function of the databaseagent. This vulnerability can be exploited by an attacker to inject arbitrary SQL queries, leading to remote code execution (RCE) through the use of PostgreSQL's large object functionality. The issue is fixed in version 0.3.0.
From the GitHub advisory
A vulnerability in the FinanceChatLlamaPack of the llama-index-packs-finchat package, versions up to v0.3.0, allows for SQL injection in the runsqlquery function of the databaseagent. This vulnerability can be exploited by an attacker to inject arbitrary SQL queries, leading to remote code execution (RCE) through the use of PostgreSQL's large object functionality.
The issue is resolved by no longer officially supporting the package and moving it into the stalepackages branch on the repo, this removing it from documentation etc.
Weakness type: CWE-89.
Product: llama-index-packs-finchat (PyPI) · Assigned by: @huntr_ai · Published: 2025-03-20
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| PyPI | llama-index-packs-finchat | <= 0.3.0 | none listed |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| run-llama | run-llama/llama_index | unspecified < 0.3.0 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| @huntr_ai | 3.0 | 10 Critical | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 10.0 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: none (no login)
- User interaction: none
- Scope: changed (can affect other components)
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc, automatable yes, technical impact total.
- FIRST EPSS (model of 2026-10-21): 1.44% probability of exploitation activity in the next 30 days; percentile 73.
Timeline
- — CVE record last updated
- — CVE record published by @huntr_ai
- — GitHub-reviewed advisory GHSA-x48g-hm9c-ww42 published (critical)
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-x48g-hm9c-ww42 github.com
- CVE.org record CVE-2024-12909 cve.org
- NVD entry CVE-2024-12909 nvd.nist.gov
Other references from the CVE record and advisory
- huntr.com huntr.com
- github.com github.com
- github.com github.com