Loading vulnerability…
CVE-2026-93834 is a use-after-free vulnerability in QEMU's 9pfs subsystem. A race between QEMU's main thread and a worker thread during concurrent processing of Tlcreate and Twalk requests can cause a guest-controlled fid path to incorporate stale heap data. An attacker can use the resulting path confusion to bypass 9p directory-traversal restrictions and access resources outside the configured shared-directory boundary.
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.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A use-after-free race condition in QEMU's 9pfs subsystem that can enable a malicious guest user to escape a shared directory boundary, read or write arbitrary host files, and potentially execute code as the QEMU process user.
A use-after-free race condition in QEMU's 9pfs subsystem that can enable a malicious guest user to bypass shared-directory traversal restrictions, read or write arbitrary host files, and execute code as the QEMU process user, resulting in VM escape.
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.