Skip to main content
Mallory
UnratedVulnerability

CVE-2026-63321: QEMU local confidentiality and availability vulnerability

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

CVE-2026-63321 affects QEMU and is rated Medium by Amazon Linux, with a CVSS v3.1 score of 5.2 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:L). The assessment indicates local exploitation by a low-privileged attacker without user interaction, potentially affecting confidentiality and availability across a security boundary. The underlying flaw, affected component, vulnerable function, and complete affected-version range are currently unavailable.

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 CVSS assessment indicates limited confidentiality loss and reduced availability, with changed scope and no integrity impact. The specific information exposed, services disrupted, and security boundary crossed are not identified. Arbitrary code execution and virtual-machine escape are not established.

Remediation

Patch, then assume compromise.

Upgrade to a release containing the fix, identified upstream in QEMU 11.0.4 and 11.1.0-rc2. For the distribution package stream using the specified version, update QEMU and related packages to 1:10.0.13+ds-0+deb13u1 or later. Amazon Linux 2023 lists this vulnerability as Pending Fix; confirm vendor-specific fixed-package availability before considering remediation complete.

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-63321 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-63321 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-63321?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-63321.
Is there a patch for CVE-2026-63321?
Upgrade to a release containing the fix, identified upstream in QEMU 11.0.4 and 11.1.0-rc2. For the distribution package stream using the specified version, update QEMU and related packages to 1:10.0.13+ds-0+deb13u1 or later.
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.