CVE-2026-50180
SQL injection allows arbitrary file reads from PostgreSQL via langroid SQLChatAgent
WAF coverage: Path traversal. WAF catches `../` patterns.
Also consider: canonical path validation · parameterized queries · ORM
Is CVE-2026-50180 being exploited?
Not confirmed. CVE-2026-50180 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.69% probability of exploitation in the next 30 days.
How severe is CVE-2026-50180?
CVE-2026-50180 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-50180?
Yes. A fix has been recorded for CVE-2026-50180. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-50180 affect?
CVE-2026-50180 affects langroid < 0.64.0, SQLChatAgent, Applications using langroid SQL features, PostgreSQL hosts connected to agent. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-50180?
Upgrade to langroid >=0.64.0; disable SQLChatAgent or restrict DB access until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker-controlled LLM output can execute SELECTs (e.g., pg_read_file) to read server files and exfiltrate data from PostgreSQL hosts.
Patch when possible
- affected< 0.64.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.