Loading vulnerability…
CVE-2026-7574 is a vulnerability in Anthropic Claude Desktop Cowork VM image handling affecting confirmed versions v1.1348.0 through v1.2278.0, including v1.1348.0, v1.1617.0, and v1.2278.0. Before booting rootfs.img, the application validates only file presence and a version marker string, but does not verify the integrity of the VM image contents at time-of-use. As a result, a local attacker who already has unprivileged code execution as the victim macOS user can tamper with the VM root filesystem image and have the modified image accepted and booted on subsequent Cowork VM launches. This is consistent with CWE-353, Missing Support for Integrity Check.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Small two-file repository containing a Bash proof-of-concept and a descriptive README for CVE-2026-7574, an integrity bypass affecting Anthropic Claude Desktop Cowork on macOS. The exploit is a local post-compromise persistence technique, not a remote exploit. The main script targets the Claude VM disk image at ~/Library/Application Support/Claude/vm_bundles/claudevm.bundle/rootfs.img, optionally backs it up, extracts an ext4 partition from the image using hardcoded dd offsets, mounts it, writes a proof file under /etc and a cron-related marker under /etc/cron.d, then reinserts the modified partition back into rootfs.img. The script finally instructs the user to boot the Cowork VM and verify that the changes persist across restarts. The README explains the vulnerability model: Claude Desktop allegedly validates image presence/version metadata but not content integrity, allowing trusted execution of a tampered VM image. Repository structure is straightforward: README.md provides vulnerability context, affected versions, impact, and mitigation guidance; CVE-2026-7574.sh is the sole executable entry point implementing the tampering workflow. No network communication, C2, or external service interaction is present; the exploit operates entirely through local filesystem access and privileged mounting/modification of the VM image.
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, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.