# CVE-2026-50180: Langroid: SQLChatAgent _validate_query blocklist misses pg_read_file family enabling arbitrary file read

> Attackers can read arbitrary files from the PostgreSQL host by bypassing SQL blocklists in Langroid's SQLChatAgent via prompt injection.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-pmch-g965-grmr, PYSEC-2026-2580

## What is CVE-2026-50180?

CVE-2026-50180 is a high-severity path traversal vulnerability in langroid, published on 9 Jul 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.64.0, `SQLChatAgent` in `langroid` ships a `_validate_query` defense-in-depth layer whose `_DANGEROUS_SQL_PATTERNS` regex blocklist enumerates dangerous SQL primitives by specific function name. The list misses the canonical PostgreSQL filesystem-disclosure family `pg_read_file()`, `pg_stat_file()`, `pg_ls_logdir()`, `pg_ls_waldir()`, `pg_current_logfile()` (and similar `SELECT`-shaped functions in the same family). It also leaves SQL Server `OPENDATASOURCE` and SQLite `ATTACH '<file>' AS x` (DATABASE keyword omitted) unblocked. An attacker able to shape the LLM's generated SQL (directly via prompt input or transitively via prompt-injection in data the LLM ingests) can read arbitrary files from the PostgreSQL host through ordinary `SELECT` queries, even with the agent's strict default configuration (`allow_dangerous_operations=False`, `allowed_statement_types=['SELECT']`). The payloads survive the statement-type allowlist (each is a `SELECT`) and pass through the regex blocklist (none of the function names match), then reach the live SQLAlchemy engine via `SQLChatAgent.run_query`. Version 0.64.0 contains a patch for the issue.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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


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

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

Upgrade langroid to 0.64.0 or later.

## Is CVE-2026-50180 being exploited?

There is no known exploitation of CVE-2026-50180 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50180 is a high-severity path traversal vulnerability in langroid, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50180 in the wild and no public exploit code.

Affected packages and fixed versions:
- langroid (PyPI): affected all versions; fixed in 0.64.0
- langroid (PyPI): affected all versions; fixed in 0.64.0
- langroid (PyPI): affected all versions; fixed in 0.64.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-50180/ (Markdown: https://insights.sbomify.com/CVE-2026-50180/index.md)
```

## Sources

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

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