Secure Boot Certificate Expiration Security Feature Bypass Vulnerability

<p>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.</p> <p>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.</p> <table> <thead> <tr> <th>Certificate Authority (CA)</th> <th>Location</th> <th>Purpose</th> <th>Expiration Date</th> </tr> </thead> <tbody> <tr> <td>Microsoft Corporation KEK CA 2011</td> <td>KEK</td> <td>Signs updates to the DB and DBX</td> <td>06/24/2026</td> </tr> <tr> <td>Microsoft Corporation UEFI CA 2011</td> <td>DB</td> <td>Signs 3rd party boot loaders, Option ROMs, etc.</td> <td>06/27/2026</td> </tr> <tr> <td>Microsoft Windows Production PCA 2011</td> <td>DB</td> <td>Signs the Windows Boot Manager</td> <td>10/19/2026</td> </tr> </tbody> </table> <p>For more information see this CVE and <a href="https://aka.ms/GetSecureBoot">Windows Secure Boot certificate expiration and CA updates</a>.</p>

Where it's fixed