Skip to main content
Mallory
UnratedVulnerability

CVE-2026-3886: QEMU virtio-gpu calc_image_hostmem Integer Overflow Guest-to-Host Code Execution

Updated 2 months 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-3886CWE-190

CVE-2026-3886 is an integer overflow vulnerability in QEMU's virtio-gpu driver, associated with calc_image_hostmem. Improper validation of user-supplied data can cause an integer overflow before buffer allocation. An attacker capable of executing low-privileged code in a guest system can exploit the flaw to execute arbitrary code in the context of the host system. The vulnerability was publicly disclosed on June 9, 2026.

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.

Successful exploitation permits privilege escalation across the guest-to-host boundary and arbitrary code execution in the host context. The specific host execution privileges and affected QEMU versions are not specified.

Mitigation

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

Until patched, reduce exposure by disabling or avoiding use of the vulnerable virtio-gpu functionality where operationally feasible, and prevent untrusted users from obtaining code execution within guest systems that can access the affected virtual device. Restrict local guest access, minimize use of shared or multi-tenant guest environments, and monitor for abnormal guest interactions with virtio-gpu devices. Specific vendor mitigation guidance beyond patching is not available in the provided content.

Remediation

Patch, then assume compromise.

Apply the QEMU update that corrects this vulnerability. For EulerOS 2.0 SP15, update the affected qemu and qemu-img packages covered by EulerOS-SA-2026-3820, whose patches were published on September 17, 2026. Fixed upstream and distribution package versions are not specified.

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-3886 exploited in the wild?
As of Oct 7, 2026, Mallory has no reports of CVE-2026-3886 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-3886?
As of Oct 7, 2026, Mallory has found no public exploit for CVE-2026-3886.
Is there a patch for CVE-2026-3886?
Apply the QEMU update that corrects this vulnerability. For EulerOS 2.0 SP15, update the affected qemu and qemu-img packages covered by EulerOS-SA-2026-3820, whose patches were published on September 17, 2026.
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 activity4Community discussion across Reddit, Mastodon, and other social sources.