Loading vulnerability…
CVE-2026-25250 is a Windows Secure Boot security feature bypass caused by a missing cryptographic step in the Secure Boot trust or verification process. The flaw affects the Secure Boot chain in a way that permits a trusted boot path to be subverted locally despite Secure Boot being enabled. Available reporting identifies it as a non-Microsoft-issued CVE that Microsoft included in Patch Tuesday guidance because exploitation impacts Windows Secure Boot behavior and may require third-party firmware or platform-specific remediation. The issue is characterized as residing in third-party firmware rather than Microsoft-developed code.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A cited example of a non-shim third-party UEFI application vulnerability that can enable Secure Boot bypass; mentioned only as background.
A non-Microsoft-issued CVE impacting Windows Secure Boot, mentioned as included among the addressed flaws.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.