Skip to main content
Mallory
UnratedVulnerability

CVE-2026-9238: Local denial of service in QEMU

Updated 3 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-9238

CVE-2026-9238 is a locally exploitable vulnerability affecting QEMU packages. Exploitation requires low privileges and no user interaction and can cause high availability impact across a security-authority boundary. Vulnerability-specific CVSS assessments disagree on integrity impact: Huawei EulerOS entries indicate none, while the Echo package-update entry indicates high impact. The underlying weakness, vulnerable function, and precise triggering conditions are not currently available.

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 cause denial of service with high availability impact and changed scope. Integrity impact is uncertain because vulnerability-specific CVSS vectors conflict. Both CVSS v3 assessments indicate no confidentiality impact. The available technical details do not establish arbitrary code execution, privilege escalation, or guest-to-host escape.

Remediation

Patch, then assume compromise.

Apply the operating-system vendor's QEMU security updates. For the Echo package-update listing, update QEMU and related packages to version 1:10.0.12+ds-0+deb13u1 or later. For Huawei EulerOS and Oracle Linux installations, install the corresponding vendor security updates; fixed package versions for those platforms are not currently available.

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-9238 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-9238 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-9238?
As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-9238.
Is there a patch for CVE-2026-9238?
Apply the operating-system vendor's QEMU security updates. For the Echo package-update listing, update QEMU and related packages to version 1:10.0.12+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.