Path Traversal in langroid (CVE-2026-50180)
Summary
Path traversal in langroid (CVE-2026-50180). Risk of unauthorized operations or information disclosure. Exploitable via SQLChatAgent. Mitigation: upgrade to 0.64.0 or later.
Original description
The description as published by the source.
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 '' 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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-50180 has been found in langroid.
Attackers can target a specific entry point like SQLChatAgent over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade langroid to 0.64.0 or later.
If unsure, ask your IT team or search "langroid CVE-2026-50180" on the vendor's site.
CVE-2026-50180 (langroid) — CWE-22
Attack surface: SQLChatAgent / langroid / _validate_query / _DANGEROUS_SQL_PATTERNS
Patched: 0.64.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in langroid. Attackers reach the vulnerable code path via SQLChatAgent.
Check the vendor advisory for the affected versions of langroid. Attack surface: SQLChatAgent / langroid / _validate_query / _DANGEROUS_SQL_PATTERNS.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.64.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'langroid' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'langroid' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
langroidを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade langroid to 0.64.0ステージング環境で 0.64.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com