CVE-2026-10797: UEFI Secure Boot revocation bypass in legacy shim
CVE-2026-10797 is a legacy flaw in the Linux shim UEFI bootloader, affecting old Microsoft-signed shim builds primarily based on version 0.9 and earlier. The vulnerability lies in shim's certificate-based revocation logic for second-stage PE bootloaders: an Authenticode-signed PE binary stores signature length information in two separate structures, and vulnerable shim code reads the signature size from the wrong PE structure during revocation checking while using different data during signature verification. By tampering with the second-stage bootloader's WIN_CERTIFICATE header, an attacker can cause shim to compare dbx or MokListX revocation entries against bogus certificate data instead of the bootloader's actual signature. This allows a revoked or otherwise blocked second-stage boot component to pass the revocation check while still being accepted as signed. In practice, the flaw undermines UEFI Secure Boot trust decisions in environments that continue to trust old Microsoft-signed shim binaries.
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 bypass of certificate-based revocation controls in the UEFI boot chain, specifically dbx and MokListX checks performed by vulnerable shim builds. An attacker can use this to load a second-stage bootloader that should have been rejected, enabling execution of untrusted code during early boot and potentially facilitating installation of persistent UEFI bootkits or other pre-OS malware. Because exploitation occurs before the operating system initializes, many host-based security controls have limited visibility into the initial execution path. The bypass affects systems that trust the relevant Microsoft third-party UEFI signing certificate regardless of the installed operating system.
Mitigation
If you can’t patch tonight, do this now.
Where immediate remediation is not possible, reduce exposure by disabling trust in Microsoft third-party UEFI signing where operationally feasible, auditing systems for legacy shim presence, and preventing unauthorized modification of EFI boot entries and EFI system partitions. Restrict administrative access and physical access because exploitation generally requires the attacker to introduce or replace boot components. Validate Secure Boot policy state, inventory the boot chain, and ensure newer protections such as MokListX enforcement and SBAT-capable components are in use. On Linux platforms, deploy available firmware revocation updates through normal vendor channels and verify revocation status with appropriate auditing tools.
Remediation
Patch, then assume compromise.
Apply the Microsoft dbx revocation update that revokes the affected legacy shim binaries, including the June 2026 revocation set referenced for this issue. Replace obsolete shim builds with current maintained versions that include the upstream fix and newer boot-chain protections. Update trusted boot applications and authorized signature databases before deploying dbx revocations to avoid boot failures. Remove outdated shim and associated second-stage bootloader binaries from installation media, recovery media, EFI system partitions, golden images, and other deployment artifacts.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-10797 exploited in the wild?
- As of Aug 11, 2026, Mallory has no reports of CVE-2026-10797 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-10797?
- As of Aug 11, 2026, Mallory has found no public exploit for CVE-2026-10797.
- Is there a patch for CVE-2026-10797?
- Apply the Microsoft dbx revocation update that revokes the affected legacy shim binaries, including the June 2026 revocation set referenced for this issue. Replace obsolete shim builds with current maintained versions that include the upstream fix and newer boot-chain protections.
Recent activity
18 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.