Langroid: Sandbox Escape to Remote Code Execution via Incomplete `eval()` Mitigation in TableChatAgent
CVE-2026-54769 · GHSA-q9p7-wqxg-mrhc · published 2026-07-06
- Severity
- Critical
- CVSS score
- 10.0
- Chance of exploitation (EPSS)
- 0.91%
- Fixed in
- 0.65.2
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Total
- CISA SSVC
This vulnerability allows a complete bypass of the presumed application boundary security logic, directly permitting Remote Code Execution (RCE). The impact stretches to unauthorized database accesses, data exfiltration, or total system compromise depending on the user environment privileges hosting the agent process.
Upgrade langroid to 0.65.2 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| langroid | PyPI | <= 0.65.1 | 0.65.2 |
- 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 has Prompt to SQL Injection, Leading to RCElangroid
- CriticalLangroid has WAF Bypass Leading to RCE in TableChatAgentlangroid
- CriticalLangroid has a Code Injection vulnerability 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.