Skip to main content
Mallory
UnratedVulnerability

CVE-2026-66022: Confidentiality and availability vulnerability in QEMU

Updated 4 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 2 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-66022

CVE-2026-66022 is a vulnerability affecting QEMU, including the QEMU package on Amazon Linux 2. Amazon Linux rates it Important with a CVSS v3.1 score of 7.8. Its underlying technical cause, vulnerable function, and precise affected-version range are not available. Upstream fixes are identified in QEMU 11.0.4 and 11.1.0-rc2.

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.

Impact

What an attacker gets, and what they’ve been doing with it.

The CVE-specific Amazon Linux CVSS v3 vector indicates high confidentiality and availability impacts, no integrity impact, and unchanged scope. The precise information exposed and mechanism of service disruption are not available. Arbitrary code execution, privilege escalation, and guest-to-host escape are not established.

Remediation

Patch, then assume compromise.

Use an upstream QEMU release containing the fix; identified fixed releases are 11.0.4 and 11.1.0-rc2. For distribution-managed installations, apply a vendor package update that explicitly addresses CVE-2026-66022. Oracle Linux 9 lists the vulnerability as addressed by ELSA-2026-500245, although the fixed package version is not available. Amazon Linux 2 fix status is inconsistent: an advisory lists a patch publication date, while a separate vulnerability entry marks the fix as pending. Confirm package availability with the vendor before treating an Amazon Linux 2 installation as remediated.

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-66022 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-66022 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-66022?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-66022.
Is there a patch for CVE-2026-66022?
Use an upstream QEMU release containing the fix; identified fixed releases are 11.0.4 and 11.1.0-rc2. For distribution-managed installations, apply a vendor package update that explicitly addresses CVE-2026-66022.
Activity feed

Recent activity

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

View more in app →
+2 more in the timeline. Sign up to see them
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 activityCommunity discussion across Reddit, Mastodon, and other social sources.