Skip to main content
Mallory
UnratedVulnerability

CVE-2026-61404: QEMU UEFI device post-load validation vulnerability

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

CVE-2026-61404 affects QEMU and is addressed by adding a post_load check to its UEFI device. The precise validation failure, vulnerable code path, exploitation mechanism, and security consequences are currently not 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.

Remediation

Patch, then assume compromise.

For Debian 13, update QEMU and its related packages to version 1:10.0.13+ds-0+deb13u1 or later. The fix adds a post_load check to QEMU's UEFI device. Fixed package versions for other distributions or Debian releases are currently not 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-61404 exploited in the wild?
As of Oct 3, 2026, Mallory has no reports of CVE-2026-61404 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-61404?
As of Oct 3, 2026, Mallory has found no public exploit for CVE-2026-61404.
Is there a patch for CVE-2026-61404?
For Debian 13, update QEMU and its related packages to version 1:10.0.13+ds-0+deb13u1 or later. The fix adds a post_load check to QEMU's UEFI device.
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.