CVE-2026-50181
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 8% of all known CVEs.
References
Related Vulnerabilities
Other CWE-22 (Path Traversal) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-23897 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2023-32315 | High | 8.6 | 100% | KEV | Fix |
| CVE-2022-29464 | Critical | 9.8 | 100% | KEV + Ransom | - |
| CVE-2021-26086 | Medium | 5.3 | 100% | KEV | Fix |
| CVE-2021-22005 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2020-5902 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
Common questions
How do I fix CVE-2026-50181?
No published fix for CVE-2026-50181 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-50181 being actively exploited?
Not that we know of. CVE-2026-50181 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.18% is the estimated probability that it will be exploited in the next 30 days. That is higher than 8% of all scored CVEs.
How severe is CVE-2026-50181?
CVE-2026-50181 has a CVSS v3 base score of 7.1, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-50181
Markdown
[](https://tridentstack.com/cve/CVE-2026-50181)HTML
<a href="https://tridentstack.com/cve/CVE-2026-50181"><img src="https://tridentstack.com/cve/badge/CVE-2026-50181.svg" alt="CVE-2026-50181"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-07-14.