Skip to main content
Mallory
UnratedVulnerability

CVE-2026-15264: QEMU vulnerability with high confidentiality, integrity, and availability impacts

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-15264

CVE-2026-15264 is a vulnerability in QEMU with potentially high confidentiality, integrity, and availability impacts. Fixes are included in QEMU 11.0.4 and 11.1.0-rc3. The affected component, vulnerable function, and underlying weakness are not specified. Severity assessments differ: one assigns CVSS v3.1 8.8 for local exploitation requiring low privileges and no user interaction, with changed scope; another assigns CVSS v3.0 9.8 for unauthenticated network exploitation.

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 may severely compromise confidentiality, integrity, and availability. The CVSS v3.1 assessment indicates impacts beyond the vulnerable component's security authority. Specific consequences such as arbitrary code execution, guest escape, or privilege escalation are not established.

Remediation

Patch, then assume compromise.

Apply the applicable vendor-provided QEMU security update. Upstream fixes are included in QEMU 11.0.4 through commit 7cd760867bdf753ac8d41c9567a1d36eb6d7aee8 and QEMU 11.1.0-rc3 through commit a113e0c53fb50d78529fd5ea79e3b8313a7ddcaa. Distribution-specific fixed 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-15264 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-15264 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-15264?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-15264.
Is there a patch for CVE-2026-15264?
Apply the applicable vendor-provided QEMU security update. Upstream fixes are included in QEMU 11.0.4 through commit 7cd760867bdf753ac8d41c9567a1d36eb6d7aee8 and QEMU 11.1.0-rc3 through commit a113e0c53fb50d78529fd5ea79e3b8313a7ddcaa.
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.