# CVE-2026-50181: Langroid: Path traversal in the file tools allows read/write outside configured current directory

> Attackers can read or write files outside the intended directory via path traversal in Langroid file tools, affecting LLM agent applications.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-fg23-3346-88f5, PYSEC-2026-2578

## What is CVE-2026-50181?

CVE-2026-50181 is a high-severity path traversal vulnerability in langroid, published on 9 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Langroid is a framework for building large-language-model-powered applications. Prior to version 0.64.0, Langroid's `ReadFileTool` and `WriteFileTool` appear to treat `curr_dir` as the intended working-directory boundary for file operations. However, the tools only change the process working directory to `curr_dir` and then operate on the user-supplied `file_path` without resolving and enforcing that the final path remains inside `curr_dir`. As a result, a tool caller can supply path traversal sequences such as `../secret.txt` to read files outside the configured current directory, or `../written_by_tool.txt` to write files outside that directory. This can impact applications that expose Langroid file tools to an LLM agent, user-controlled tool call, or delegated coding/documentation agent while relying on `curr_dir` to restrict file access to a project/workspace directory. Version 0.64.0 patches the issue.

Weakness: CWE-23 (Relative Path Traversal), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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


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

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

Upgrade langroid to 0.64.0 or later.

## Is CVE-2026-50181 being exploited?

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

Public exploit code:

- CVE-2026-50181 / GHSA-fg23-3346-88f5: Langroid path traversal advisory landing page (github_poc): https://github.com/chaitanyagarware/CVE-2026-50181

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50181 is a high-severity path traversal vulnerability in langroid, published on 9 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50181 exists.

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

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

## Sources

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

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