Loading vulnerability…
CVE-2026-50158 is an arbitrary file write vulnerability in the yutu MCP caption-download tool. The flaw arises because the user-controlled file parameter is passed directly to file creation logic via os.Create() without confinement to the intended YUTU_ROOT directory boundary. As a result, an attacker who can invoke the tool can cause yutu to create or truncate files at attacker-selected filesystem paths writable by the yutu process. The issue is caused by improper restriction of externally controlled file paths, allowing writes outside the expected root-scoped workspace.
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.
YUTU_ROOT isolation boundary and can cause denial of service through destructive file corruption.If you can’t patch tonight, do this now.
caption-download tool. Run the yutu process with least-privilege filesystem permissions and, where possible, sandbox it so it cannot write to sensitive locations outside its intended working directory. Additional compensating controls include mandatory authentication, network access restrictions, and filesystem-level confinement.Patch, then assume compromise.
0.10.9-dev1 or later. The vulnerable file creation logic should be changed from direct use of os.Create() on attacker-supplied paths to a root-confined file open mechanism that enforces writes within YUTU_ROOT, such as using the package root abstraction to open files relative to the allowed directory. Review any related file-handling paths for similar boundary bypass conditions and validate that path traversal and absolute-path writes are rejected.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.