Skip to main content
Mallory
UnratedVulnerability

CVE-2026-8343: Local Integrity and Availability Vulnerability in QEMU

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

CVE-2026-8343 affects QEMU and allows a low-privileged local attacker to cause high integrity and availability impacts without user interaction. Its CVSS v3 base score is 8.4, with changed scope and no confidentiality impact. The vulnerable component, function, and underlying weakness have not been identified. The vulnerability is addressed in QEMU package version 1:10.0.11+ds-0+deb13u1 or later for the applicable distribution.

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 can severely compromise integrity and availability, with effects extending beyond the vulnerable component's security authority, as indicated by the changed-scope CVSS assessment. No confidentiality impact is identified. Specific consequences, such as arbitrary code execution or virtual-machine escape, are not established.

Remediation

Patch, then assume compromise.

Update QEMU and its related packages to version 1:10.0.11+ds-0+deb13u1 or later on systems using that package versioning scheme. For other distributions, install the corresponding vendor security update; the 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-8343 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-8343 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-8343?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-8343.
Is there a patch for CVE-2026-8343?
Update QEMU and its related packages to version 1:10.0.11+ds-0+deb13u1 or later on systems using that package versioning scheme. For other distributions, install the corresponding vendor security update; the fixed package versions are not specified.
Activity feed

Recent activity

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

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