Loading vulnerability…
CVE-2026-61476 is a medium-severity vulnerability affecting QEMU packages. The available technical information does not identify the vulnerable function or flaw class. Upstream fixes are present in QEMU v11.0.4 and v11.1.0-rc2. Amazon Linux identifies its affected qemu packages in Amazon Linux 2 Core and Amazon Linux 2023 as awaiting fixes; Amazon Linux 2 Core qemu-guest-agent and qemu-kvm packages are not affected.
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 public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A medium-severity QEMU vulnerability with an Amazon Linux CVSS v3.1 score of 6.5 (AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H), indicating a local, low-complexity attack requiring low privileges that can cause high availability impact across a changed security scope. The issue is fixed in QEMU v11.1.0-rc2 and v11.0.4; Amazon Linux 2 Core qemu is listed as pending a fix.
An unpatched vulnerability identified as CVE-2026-61476 affecting Debian Linux 11.0, 12.0, and 13.0. The content provides no technical description of the flaw's impact or attack vector.
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.