# CVE-2026-25481: Langroid has WAF Bypass Leading to RCE in TableChatAgent

> Attackers can bypass WAF restrictions in TableChatAgent to execute arbitrary code via unsafe pandas_eval expressions.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Feb 2026
- **Updated:** 4 Feb 2026
- **Also known as:** GHSA-x34r-63hx-w57f, PYSEC-2026-383

## What is CVE-2026-25481?

CVE-2026-25481 is a critical code injection vulnerability in langroid, published on 4 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Langroid is a framework for building large-language-model-powered applications. Prior to version 0.59.32, there is a bypass to the fix for CVE-2025-46724. TableChatAgent can call pandas_eval tool to evaluate the expression. There is a WAF in langroid/utils/pandas_utils.py introduced to block code injection CVE-2025-46724. However it can be bypassed due to _literal_ok() returning False instead of raising UnsafeCommandError on invalid input, combined with unrestricted access to dangerous dunder attributes (__init__, __globals__, __builtins__). This allows chaining whitelisted DataFrame methods to leak the eval builtin and execute arbitrary code. This issue has been patched in version 0.59.32.

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

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

3 open source packages ship an affected version, including langroid. It affects 1 product.


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

Products: Langroid Langroid.

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

Upgrade langroid to 0.59.32 or later.

## Is CVE-2026-25481 being exploited?

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

## Other vulnerabilities in langroid

- [CVE-2025-46724](https://insights.sbomify.com/CVE-2025-46724/): Langroid has a Code Injection vulnerability in TableChatAgent (critical 9.8)
- [CVE-2025-46725](https://insights.sbomify.com/CVE-2025-46725/): Langroid has a Code Injection vulnerability in LanceDocChatAgent through vector_store (high 8.1)
- [CVE-2025-46726](https://insights.sbomify.com/CVE-2025-46726/): Langroid Vulnerable to XXE Injection via XMLToolMessage (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25481 is a critical code injection vulnerability in langroid, published on 4 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25481 exists.

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

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

## Sources

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

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