Loading vulnerability…
CVE-2026-50181 is a path traversal vulnerability in Langroid prior to version 0.64.0 affecting the ReadFileTool and WriteFileTool. The tools appear to use curr_dir as a workspace boundary for file access, but they only change the process working directory and then operate on the caller-supplied path without resolving the final canonical path and verifying that it remains within the intended base directory. Because traversal sequences and other escaping path forms are not properly constrained, an attacker or tool caller can cause file operations to target locations outside the configured workspace. In exposed agentic workflows, this breaks the assumed filesystem sandbox and can allow unauthorized reads and writes beyond the intended project directory.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
curr_dir alone as a security boundary in vulnerable versions. Where untrusted users, LLM agents, or delegated tools can influence file tool arguments, disable or strictly restrict ReadFileTool, WriteFileTool, and similar filesystem-capable tools until patched. As a compensating control, implement canonical path validation that rejects traversal attempts, absolute-path escapes, and symlink-based escapes before performing filesystem operations, and run the application with the minimum filesystem privileges necessary.Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.