Skip to main content
Mallory
UnratedVulnerability

CVE-2026-63323: QEMU vulnerability (CVE-2026-63323)

Updated 5 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-63323

CVE-2026-63323 is a vulnerability in QEMU addressed in versions 11.0.4 and 11.1.0-rc2. Its vulnerability-specific CVSS v3.0 assessment indicates low-complexity network exploitation without authentication or user interaction, with potentially high confidentiality, integrity, and availability impacts. The underlying flaw, vulnerable function, and affected QEMU configurations are not specified.

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 vulnerability-specific CVSS v3.0 vector indicates high confidentiality, integrity, and availability impacts with unchanged scope, corresponding to a base score of 9.8. The precise consequences, including whether exploitation enables code execution, information disclosure, or a particular form of service disruption, are not established.

Remediation

Patch, then assume compromise.

Upgrade to QEMU 11.0.4 or another release containing the fix; the fix is also included in 11.1.0-rc2. The corresponding upstream commits are a7f027cff81c8047707d574f0e4ec57e66c63452 and 5cc182ba39a3ca8ec9ba0576de9696be76dc087d. For distribution-managed installations, install the applicable vendor security update. Amazon Linux 2023 QEMU is listed as pending a fix; Amazon Linux 2 qemu, qemu-guest-agent, and qemu-kvm are listed as not affected. Distribution-specific fixed package versions are not available.

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-63323 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-63323 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-63323?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-63323.
Is there a patch for CVE-2026-63323?
Upgrade to QEMU 11.0.4 or another release containing the fix; the fix is also included in 11.1.0-rc2. The corresponding upstream commits are a7f027cff81c8047707d574f0e4ec57e66c63452 and 5cc182ba39a3ca8ec9ba0576de9696be76dc087d.
Activity feed

Recent activity

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

View more in app →
+1 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.