Langroid has a Code Injection vulnerability in TableChatAgent
CVE-2025-46724 · GHSA-jqq5-wc57-f8hj · published 2025-05-20 · updated 2026-07-01
- Severity
- Critical
- CVSS score
- 9.8
- Chance of exploitation (EPSS)
- 0.83%
- Fixed in
- 0.53.15
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Total
- CISA SSVC
Confidentiality, Integrity and Availability of the system hosting the LLM application.
Upgrade langroid to 0.53.15 or later.
Langroid 0.53.15 sanitizes input to TableChatAgent by default to tackle the most common attack vectors, and added several warnings about the risky behavior in the project documentation.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| langroid | PyPI | < 0.53.15 | 0.53.15 |
- CriticalUnauthenticated Remote Code Execution in Langflow via Public Flow Build EndpointlangflowExploited
- CriticalRay is vulnerable to Critical RCE via Safari & Firefox Browsers through DNS Rebinding AttackrayExploited
- CriticalLangflow Unauth RCElangflow, langflow-baseExploited
- HighLiteLLM: Authenticated command execution via MCP stdio test endpointslitellmExploited
- CriticalMLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifacmlflow
- CriticalAgno: Arbitrary code execution via `eval()` on `field_type` in `FunctionCall`agno
- CriticalLangroid: Neo4jChatAgent executes LLM-generated Cypher without validation (prompt-to-Cypher injection; config-conditional RCE), mirroring thlangroid
- CriticalLangroid: SQLChatAgent dangerous-function blocklist can be bypassed with quoted or schema-qualified pg_read_file callslangroid
- CriticalLangroid: Sandbox Escape to Remote Code Execution via Incomplete `eval()` Mitigation in TableChatAgentlangroid
- CriticalLangroid has Prompt to SQL Injection, Leading to RCElangroid
- CriticalLangroid has WAF Bypass Leading to RCE in TableChatAgentlangroid
- HighLangroid: handle_message() executes user-supplied tool JSON without sender verificationlangroid
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.