Secure Boot Certificate Expiration Security Feature Bypass Vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 10.0.14393.8783, 10.0.17763.8276, 10.0.19044.6809, 10.0.19045.6809, 10.0.22631.6491, and 7 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Microsoft Windows 10 Version 1607
From 10.0.14393.0 · fixed in 10.0.14393.8783
- Microsoft Windows 10 Version 1809
From 10.0.17763.0 · fixed in 10.0.17763.8276
- Microsoft Windows 10 Version 21H2
From 10.0.19044.0 · fixed in 10.0.19044.6809
- Microsoft Windows 10 Version 22H2
From 10.0.19045.0 · fixed in 10.0.19045.6809
- Microsoft Windows 11 version 23H2
From 10.0.22631.0 · fixed in 10.0.22631.6491
- Microsoft Windows 11 Version 23H2
From 10.0.22631.0 · fixed in 10.0.22631.6491
- Microsoft Windows 11 Version 24H2
From 10.0.26100.0 · fixed in 10.0.26100.7623
- Microsoft Windows 11 Version 25H2
From 10.0.26200.0 · fixed in 10.0.26200.7623
- Microsoft Windows Server 2012
From 6.2.9200.0 · fixed in 6.2.9200.25868
- Microsoft Windows Server 2012 (Server Core installation)
From 6.2.9200.0 · fixed in 6.2.9200.25868
- Microsoft Windows Server 2012 R2
From 6.3.9600.0 · fixed in 6.3.9600.22968
- Microsoft Windows Server 2012 R2 (Server Core installation)
From 6.3.9600.0 · fixed in 6.3.9600.22968
- Microsoft Windows Server 2016
From 10.0.14393.0 · fixed in 10.0.14393.8783
- Microsoft Windows Server 2016 (Server Core installation)
From 10.0.14393.0 · fixed in 10.0.14393.8783
- Microsoft Windows Server 2019
From 10.0.17763.0 · fixed in 10.0.17763.8276
- Microsoft Windows Server 2019 (Server Core installation)
From 10.0.17763.0 · fixed in 10.0.17763.8276
- Microsoft Windows Server 2022
From 10.0.20348.0 · fixed in 10.0.20348.4648
- Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)
From 10.0.25398.0 · fixed in 10.0.25398.2092
- Microsoft Windows Server 2025
From 10.0.26100.0 · fixed in 10.0.26100.32230
- Microsoft Windows Server 2025 (Server Core installation)
From 10.0.26100.0 · fixed in 10.0.26100.32230