Skip to main content
Mallory
UnratedVulnerability

CVE-2026-66020: QEMU virtio-gpu blob scanout mapping cleanup vulnerability

Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-66020

CVE-2026-66020 is a vulnerability in QEMU associated with virtio-gpu blob scanouts during mapping cleanup. The upstream fix disables blob scanouts when mappings are cleaned up and is identified as included in QEMU 10.0.14. The precise underlying weakness and exploitation consequences are not established by the available technical information.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Remediation

Patch, then assume compromise.

Upgrade to a QEMU release containing the upstream fix, identified as QEMU 10.0.14, or install the corresponding distribution security update. For Echo packages, update QEMU and related packages to version 1:10.0.13+ds-0+deb13u1+e2 or later. A separate Debian-related advisory reports no vendor-supplied patch or known solution for the packages it covers; confirm fix availability for the specific distribution and release.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-66020 exploited in the wild?
As of Oct 9, 2026, Mallory has no reports of CVE-2026-66020 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-66020?
As of Oct 9, 2026, Mallory has found no public exploit for CVE-2026-66020.
Is there a patch for CVE-2026-66020?
Upgrade to a QEMU release containing the upstream fix, identified as QEMU 10.0.14, or install the corresponding distribution security update. For Echo packages, update QEMU and related packages to version 1:10.0.13+ds-0+deb13u1+e2 or later.
Activity feed

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.