IT

Tracker / CVE-2026-21265

CVE-2026-21265

Medium 6.4

Windows Secure Boot stores Microsoft certificates in the UEFI KEK and DB. These original certificates are approaching expiration, and devices containing affected certificate versions must update them to maintain Secure Boot functionality and avoid compromising security by losing security fixes related to Windows boot manager or Secure Boot. The operating system’s certificate update protection mechanism relies on firmware components that might contain defects, which can cause certificate trust updates to fail or behave unpredictably. This leads to potential disruption of the Secure Boot trust chain and requires careful validation and deployment to restore intended security guarantees. Certificate Authority (CA) Location Purpose Expiration Date Microsoft Corporation KEK CA 2011 KEK Signs updates to the DB and DBX 06/24/2026 Microsoft Corporation UEFI CA 2011 DB Signs 3rd party boot loaders, Option ROMs, etc. 06/27/2026 Microsoft Windows Production PCA 2011 DB Signs the Windows Boot Manager 10/19/2026 For more information see this CVE and Windows Secure Boot certificate expiration and CA updates.

Affected products and versions

microsoft windows_10_1607 · … → 10.0.14393.8783
microsoft windows_10_1809 · … → 10.0.17763.8276
microsoft windows_10_21h2 · … → 10.0.19044.6809
microsoft windows_10_22h2 · … → 10.0.19045.6809
microsoft windows_11_23h2 · … → 10.0.22631.6491
microsoft windows_11_24h2 · … → 10.0.26100.7623
microsoft windows_11_25h2 · … → 10.0.26200.7623
microsoft windows_server_2012
microsoft windows_server_2016 · … → 10.0.14393.8783
microsoft windows_server_2019 · … → 10.0.17763.8276
microsoft windows_server_2022 · … → 10.0.20348.4648
microsoft windows_server_2022_23h2 · … → 10.0.25398.2092
microsoft windows_server_2025 · … → 10.0.26100.32230

Analysis

This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.

References