Cloud Hypervisor versions 34.0 through 50.0 contain an arbitrary host file exfiltration issue when virtio-block devices are backed by raw images and image format auto-detection is used. A malicious guest can overwrite the beginning of its disk (the disk header) with a crafted QCOW2 structure that references a sensitive host filesystem path. On a subsequent VM boot or disk scan, Cloud Hypervisor’s image format auto-detection parses the attacker-controlled header and follows the embedded host path, resulting in the contents of the referenced host file being served back to the guest as if it were part of the disk image. Guest-initiated VM reboots are sufficient to trigger the disk scan without terminating the Cloud Hypervisor process, enabling exploitation without management-stack interaction. Exposure is constrained by the Cloud Hypervisor process privileges and filesystem access.
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.
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.
3 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.