Skip to main content
Mallory
UnratedVulnerability

CVE-2026-63320: QEMU virtio-net Receive Filtering Heap Out-of-Bounds Read

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

CVE-2026-63320 is a host-side heap out-of-bounds read in QEMU's virtio-net receive-filtering implementation. The issue was observed with a virtio-net-pci device on the q35 machine model, where AddressSanitizer detected a heap-buffer-overflow read and a crash in receive_filter(). Processing network traffic through the affected receive-filtering path can cause a denial of service. Upstream fixes are included 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.

Exploitation can cause a host-side QEMU process crash, disrupting the affected virtual machine's availability. The vulnerability-specific Amazon Linux assessment assigns CVSS v3.1 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L), indicating unauthenticated network exploitation with low availability impact and no assessed confidentiality or integrity impact. Code execution, information disclosure, and compromise of the host operating system are not established.

Mitigation

If you can’t patch tonight, do this now.

Until patched packages can be installed, restrict untrusted network traffic reaching affected virtual network interfaces and limit access to affected virtualization hosts. No vulnerability-specific workaround is established.

Remediation

Patch, then assume compromise.

Upgrade to QEMU 11.0.4, 11.1.0-rc2, or a later release containing the fix, or install the distribution's patched QEMU packages. Amazon Linux updates addressing the issue are covered by ALAS2-2026-4009 and ALAS2023-2026-3241; Oracle Linux 9 includes the fix in ELSA-2026-500245. Confirm package availability and fixed versions for the specific distribution release, since some package records identify pending fixes.

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-63320 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-63320 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-63320?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-63320.
Is there a patch for CVE-2026-63320?
Upgrade to QEMU 11.0.4, 11.1.0-rc2, or a later release containing the fix, or install the distribution's patched QEMU packages. Amazon Linux updates addressing the issue are covered by ALAS2-2026-4009 and ALAS2023-2026-3241; Oracle Linux 9 includes the fix in ELSA-2026-500245.
Activity feed

Recent activity

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

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