# CVE-2026-54769: Langroid: Sandbox Escape to Remote Code Execution via Incomplete `eval()` Mitigation in TableChatAgent

> Attackers can achieve remote code execution by exploiting incomplete sandboxing in eval() when processing LLM outputs in Langroid.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **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-q9p7-wqxg-mrhc, PYSEC-2026-2581

## What is CVE-2026-54769?

CVE-2026-54769 is a critical code injection 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. Versions prior to 0.65.2 are vulnerable to a critical Sandbox Escape leading to Remote Code Execution (RCE) in its `TableChatAgent` and `VectorStore` capabilities. When these agents evaluate LLM-generated tool messages with `full_eval=True`, they attempt to sandbox the execution by explicitly setting `locals` to an empty dictionary `{}` inside Python's `eval()` function. However, this relies on an incomplete understanding of Python's execution model. Because `__builtins__` is not explicitly scrubbed from the `globals` dictionary mapping, Python implicitly injects all built-ins during execution, granting full access to functions like `__import__('os').system()`. Since `TableChatAgent.pandas_eval()` executes external LLM outputs natively, this bypass permits any attacker providing prompt payload to achieve unauthenticated RCE on the host system. Version 0.65.2 patches the issue.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

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


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

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

Upgrade langroid to 0.65.2 or later.

## Is CVE-2026-54769 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54769 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54769 is a critical code injection 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54769 exists.

Affected packages and fixed versions:
- langroid (PyPI): affected all versions; fixed in 0.65.2
- langroid (PyPI): affected all versions; fixed in 0.65.2
- langroid (PyPI): affected all versions; fixed in 0.65.2

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-54769/ (Markdown: https://insights.sbomify.com/CVE-2026-54769/index.md)
```

## Sources

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

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