CVE-2026-21265 | Secure Boot Certificate Expiration Security Feature Bypass Vulnerability

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.

Published: 2026-01-13 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-21265 is rated Moderate Risk (46.3/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.97%). Mandatory action: Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-21265

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.21% 0.97% +0.75%
2 2026-06-12 0.30% 0.21% -0.09%
3 2026-06-11 0.30%

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-21265

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.4 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
0.5 5.9 [email protected]

Weakness enumeration for CVE-2026-21265

OS Trackers for CVE-2026-21265

vendor priority summary link
ubuntu medium CVE-2026-21265 medium priority: Ubuntu including 3 source packages (secureboot-db, shim, shim-signed), 24 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): not-affected 15, ignored 6, needs-triage 3. https://ubuntu.com/security/CVE-2026-21265

Affected software / configurations for CVE-2026-21265

Vendor Product Version Raw CPE
microsoft windows_10_1607 < 10.0.14393.8783 cpe:2.3:o:microsoft:windows_10_1607:*:*:*:*:*:*:x64:*
microsoft windows_10_1607 < 10.0.14393.8783 cpe:2.3:o:microsoft:windows_10_1607:*:*:*:*:*:*:x86:*
microsoft windows_10_1809 < 10.0.17763.8276 cpe:2.3:o:microsoft:windows_10_1809:*:*:*:*:*:*:x64:*
microsoft windows_10_1809 < 10.0.17763.8276 cpe:2.3:o:microsoft:windows_10_1809:*:*:*:*:*:*:x86:*
microsoft windows_10_21h2 < 10.0.19044.6809 cpe:2.3:o:microsoft:windows_10_21h2:*:*:*:*:*:*:arm64:*
microsoft windows_10_21h2 < 10.0.19044.6809 cpe:2.3:o:microsoft:windows_10_21h2:*:*:*:*:*:*:x64:*
microsoft windows_10_21h2 < 10.0.19044.6809 cpe:2.3:o:microsoft:windows_10_21h2:*:*:*:*:*:*:x86:*
microsoft windows_10_22h2 < 10.0.19045.6809 cpe:2.3:o:microsoft:windows_10_22h2:*:*:*:*:*:*:arm64:*
microsoft windows_10_22h2 < 10.0.19045.6809 cpe:2.3:o:microsoft:windows_10_22h2:*:*:*:*:*:*:x64:*
microsoft windows_10_22h2 < 10.0.19045.6809 cpe:2.3:o:microsoft:windows_10_22h2:*:*:*:*:*:*:x86:*
microsoft windows_11_23h2 < 10.0.22631.6491 cpe:2.3:o:microsoft:windows_11_23h2:*:*:*:*:*:*:arm64:*
microsoft windows_11_23h2 < 10.0.22631.6491 cpe:2.3:o:microsoft:windows_11_23h2:*:*:*:*:*:*:x64:*
microsoft windows_11_24h2 < 10.0.26100.7623 cpe:2.3:o:microsoft:windows_11_24h2:*:*:*:*:*:*:arm64:*
microsoft windows_11_24h2 < 10.0.26100.7623 cpe:2.3:o:microsoft:windows_11_24h2:*:*:*:*:*:*:x64:*
microsoft windows_11_25h2 < 10.0.26200.7623 cpe:2.3:o:microsoft:windows_11_25h2:*:*:*:*:*:*:arm64:*
microsoft windows_11_25h2 < 10.0.26200.7623 cpe:2.3:o:microsoft:windows_11_25h2:*:*:*:*:*:*:x64:*
microsoft windows_server_2012 cpe:2.3:o:microsoft:windows_server_2012:-:*:*:*:*:*:*:*
microsoft windows_server_2012 r2 cpe:2.3:o:microsoft:windows_server_2012:r2:*:*:*:*:*:*:*
microsoft windows_server_2016 < 10.0.14393.8783 cpe:2.3:o:microsoft:windows_server_2016:*:*:*:*:*:*:*:*
microsoft windows_server_2019 < 10.0.17763.8276 cpe:2.3:o:microsoft:windows_server_2019:*:*:*:*:*:*:*:*
microsoft windows_server_2022 < 10.0.20348.4648 cpe:2.3:o:microsoft:windows_server_2022:*:*:*:*:*:*:*:*
microsoft windows_server_2022_23h2 < 10.0.25398.2092 cpe:2.3:o:microsoft:windows_server_2022_23h2:*:*:*:*:*:*:*:*
microsoft windows_server_2025 < 10.0.26100.32230 cpe:2.3:o:microsoft:windows_server_2025:*:*:*:*:*:*:*:*

References for CVE-2026-21265

cvelogic Threat Intelligence