Skip to main content
Mallory
HighVulnerability

CVE-2026-8863: UEFI Secure Boot Bypass in Microsoft-Signed Legacy Shim Bootloaders

Published Jun 9, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS0.11%1st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-8863CWE-693

CVE-2026-8863 is a UEFI Secure Boot security feature bypass affecting multiple legacy Microsoft-signed shim bootloaders, primarily shim version 0.9 and earlier. On UEFI-based systems that trust the Microsoft Corporation UEFI CA 2011 third-party certificate, these old shim binaries remain accepted as valid first-stage bootloaders and can be introduced by an attacker even if the original software package is not installed on the target. The weakness allows an attacker to use an outdated but still-trusted shim to transfer trust to vulnerable or revoked second-stage boot components, especially GRUB 2, or to bypass newer boot-chain protections absent from legacy shim generations, including Machine Owner Key denylist enforcement and Secure Boot Advanced Targeting checks. As a result, Secure Boot can be defeated without requiring a memory-corruption exploit, enabling execution of untrusted code in the pre-OS boot chain.

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 allows execution of arbitrary untrusted code during the early boot phase before the operating system and most host security controls initialize. This can be used to bypass Secure Boot policy, load unsigned or otherwise untrusted boot components, and install persistent UEFI bootkits or other pre-OS malware. Because execution occurs before OS startup, the compromise can evade many endpoint protections and can provide durable persistence across operating system reinstallation or disk replacement if malicious firmware- or boot-level components are established.

Mitigation

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

Until full remediation is deployed, restrict administrative access and prevent unauthorized modification of the EFI System Partition and boot configuration. Disable trust for third-party UEFI signing where operationally possible, especially on systems that do not require it. Audit the boot chain for legacy shim and GRUB components, remove outdated boot media from circulation, and validate that revocation updates are present across physical, virtual, and cloud-hosted systems. Prioritize environments where attackers could gain local administrator privileges, physical access, or other means to alter boot components.

Remediation

Patch, then assume compromise.

Apply the vendor-provided June 2026 security updates and, critically, the corresponding UEFI DBX revocation update that blocks the vulnerable Microsoft-signed shim bootloaders. Ensure trusted boot applications are updated before or in coordination with DBX deployment so legitimate boot components are not rejected after revocation. On Linux and other non-Windows environments, obtain and deploy the relevant firmware revocation updates through supported vendor channels and remove obsolete shim and second-stage bootloader binaries from installation media, recovery media, and deployment images.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
FAQ

Frequently asked questions

Is CVE-2026-8863 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-8863 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-8863?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-8863.
Is there a patch for CVE-2026-8863?
Apply the vendor-provided June 2026 security updates and, critically, the corresponding UEFI DBX revocation update that blocks the vulnerable Microsoft-signed shim bootloaders. Ensure trusted boot applications are updated before or in coordination with DBX deployment so legitimate boot components are not rejected after revocation.
How severe is CVE-2026-8863?
CVE-2026-8863 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.11% (1st percentile) as of Sep 25, 2026.
Activity feed

Recent activity

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

View more in app →
+6 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 malware13Malware 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 activity9Community discussion across Reddit, Mastodon, and other social sources.