Quick answers
- Is CVE-2026-50181 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50181 being exploited in the wild.
- How severe is CVE-2026-50181?
- High severity, with a CVSS score of 7.1, published 10 July 2026.
- Which products and versions are affected?
- langroid (PyPI) <= 0.63.0, ECOSYSTEM:introduced=0,fixed=0.64.0.
- Is there a fix for CVE-2026-50181?
- Yes. langroid (PyPI): upgrade to 0.64.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-50181 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-50181?
- Check whether you run langroid (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- langroid (PyPI): upgrade to 0.64.0 or later
pip install "langroid>=0.64.0"
Technical details
A path traversal vulnerability exists in Langroid's `ReadFileTool` and `WriteFileTool` components prior to version 0.64.0. While these tools attempt to restrict operations to a specific directory (`curr_dir`) by changing the process working directory, they fail to resolve and validate the user-supplied `file_path`. An attacker or a malicious LLM agent can provide relative path sequences (e.g., `../etc/passwd`) to escape the intended sandbox. This allows for unauthorized reading of sensitive files or writing of arbitrary files on the local filesystem where the agent is running. The issue is addressed in version 0.64.0 by implementing path resolution and boundary enforcement.
Affected products
- langroid langroid < 0.64.0
Identifiers
- CVE-2026-50181
- GHSA-fg23-3346-88f5
- PYSEC-2026-2578
Timeline
- 2026-05-28: advisory: GitHub Security Advisory published
- 2026-07-10: disclosed: NVD publication date
- 2026-06-01: patched: Version 0.64.0 released to address the issue