# CVE-2026-25879: Langroid has Prompt to SQL Injection, Leading to RCE

> Attackers can achieve remote code execution on the database host via prompt injection in Langroid's SQLChatAgent when dangerous database privileges are enabled.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Jun 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-mxfr-6hcw-j9rq, PYSEC-2026-382

## What is CVE-2026-25879?

CVE-2026-25879 is a critical SQL injection vulnerability in langroid, published on 1 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Langroid is a framework for building large-language-model-powered applications. Prior to version 0.63.0, SQLChatAgent executes SQL produced by an LLM, which is influenceable by prompt injection. When configured with a database role that has privileges enabling code execution or filesystem access (e.g., PostgreSQL pg_execute_server_program, MySQL FILE, MSSQL xp_cmdshell), an attacker who can shape the agent's input — including indirectly via data returned to the LLM — can coerce execution of dialect-specific primitives such as `COPY ... FROM PROGRAM`, achieving RCE on the database host. Fixed in v0.63.0 by defaulting SQLChatAgent to a SELECT-only sqlglot-parsed statement allowlist with a dialect-aware dangerous-pattern blocklist; allow_dangerous_operations=True restores the previous unrestricted behavior for trusted deployments.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-25879?

3 open source packages ship an affected version, including langroid.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `langroid` | PyPI | All versions | 0.63.0 |
| `langroid` | PyPI | All versions | 0.63.0 |
| `langroid` | PyPI | All versions | 0.63.0 |

## How do I fix CVE-2026-25879?

Upgrade langroid to 0.63.0 or later.

## Is CVE-2026-25879 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25879 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25879 and fix it if it is affected.

What it is: CVE-2026-25879 is a critical SQL injection vulnerability in langroid, published on 1 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25879 exists.

Affected packages and fixed versions:
- langroid (PyPI): affected all versions; fixed in 0.63.0
- langroid (PyPI): affected all versions; fixed in 0.63.0
- langroid (PyPI): affected all versions; fixed in 0.63.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25879/ (Markdown: https://insights.sbomify.com/CVE-2026-25879/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25879
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25879
- OSV: https://osv.dev/vulnerability/CVE-2026-25879

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25879/
Summaries are generated and may contain mistakes; the official description above is the record.