No cwe for this issue in Windows Secure Boot allows an authorized attacker to bypass a security feature locally.
The product does not check or incorrectly checks the revocation status of a certificate, which may cause it to use a certificate that has been compromised.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Windows_10_1607 | Microsoft | * | 10.0.14393.9612 (excluding) |
| Windows_10_1809 | Microsoft | * | 10.0.17763.9376 (excluding) |
| Windows_10_21h2 | Microsoft | * | 10.0.19044.7807 (excluding) |
| Windows_10_22h2 | Microsoft | * | 10.0.19045.7807 (excluding) |
| Windows_11_23h2 | Microsoft | * | 10.0.22631.7652 (excluding) |
| Windows_11_24h2 | Microsoft | * | 10.0.26100.9711 (excluding) |
| Windows_11_25h2 | Microsoft | * | 10.0.26200.9711 (excluding) |
| Windows_11_26h1 | Microsoft | * | 10.0.28000.3231 (excluding) |
| Windows_11_26h2 | Microsoft | * | 10.0.26300.9711 (excluding) |
| Windows_server_2016 | Microsoft | * | 10.0.14393.9612 (excluding) |
| Windows_server_2019 | Microsoft | * | 10.0.17763.9376 (excluding) |
| Windows_server_2022 | Microsoft | * | 10.0.20348.5761 (excluding) |
| Windows_server_2025 | Microsoft | * | 10.0.26100.33650 (excluding) |