Full Report
Microsoft has released the Windows 10 KB5075912 extended security update to fix February 2026 Patch Tuesday vulnerabilities, including six zero-days, and continue rolling out replacements for expiring Secure Boot certificates. [...]
Analysis Summary
This summary is based solely on the provided context, which details the release of an Extended Security Update (ESU) containing numerous vulnerability fixes, including six zero-days. Specific CVE IDs, CVSS scores, and detailed technical descriptions for the individual vulnerabilities are *not* present in the source text, so those fields will reflect their absence.
# Vulnerability: February 2026 Patch Tuesday Vulnerabilities and Secure Boot Update
## CVE Details
- CVE ID: **Not specified in the source material.** (The update fixes February 2026 Patch Tuesday vulnerabilities, including six zero-days.)
- CVSS Score: **Not specified in the source material.**
- CWE: **Not specified in the source material.**
## Affected Systems
- Products: Windows 10 (General), Windows 10 Enterprise LTSC, Windows 10 Enterprise LTSC 2021.
- Versions:
- General Windows 10 (post-update): Build 19045.6937
- Windows 10 Enterprise LTSC 2021 (post-update): Build 19044.6937
- Configurations: Systems with Secure Launch and Virtual Secure Mode (VSM) enabled may have experienced shutdown/hibernation issues prior to this patch.
## Vulnerability Description
The KB5075912 update addresses **58 vulnerabilities** from the February 2026 Patch Tuesday cycle, **including six actively exploited zero-day flaws**. The context does not list the specific CVEs or technical details of these flaws, only that they are fixed.
Additionally, this update fixes a known issue causing Secure Launch/VSM-enabled PCs to restart instead of shutting down or hibernating after previous updates. It also continues the rollout of replacement Secure Boot certificates to prevent security validation failures starting in June 2026.
## Exploitation
- Status: **Not enough information provided.** (The update fixes six zero-days, implying some were likely exploited in the wild prior to patching.)
- Complexity: **Not specified in the source material.**
- Attack Vector: **Not specified in the source material.**
## Impact
- Confidentiality: **Not specified in the source material (applies to the fixed zero-days).**
- Integrity: **Not specified in the source material (applies to the fixed zero-days).**
- Availability: **Not specified in the source material (applies to the fixed zero-days).** (Note: A separate known issue *did* impact availability/operability by preventing shutdowns/hibernation.)
## Remediation
### Patches
- **KB5075912** for Windows 10 (Resulting in build 19045.6937)
- **KB5075912** for Windows 10 Enterprise LTSC 2021 (Resulting in build 19044.6937)
### Workarounds
- Microsoft states there are **no known issues** with this update.
- No specific workarounds for the zero-day vulnerabilities are detailed, pending installation of KB5075912.
## Detection
- **Indicators of Compromise (IoCs):** None provided; IoCs would depend on knowledge of the six specific zero-day CVEs.
- **Detection Methods and Tools:** Systems should be checked for the installation status of update KB5075912. Monitoring for unexpected restarts on systems utilizing Secure Launch/VSM before the update is applied may indicate the known bug.
## References
- Microsoft Support KB Article: hxxps://support.microsoft.com/en-us/topic/february-10-2026-kb5075912-os-builds-19045-6937-and-19044-6937-df558259-6b48-41ef-8601-6e75bb790e0e
- Microsoft warnings on expiring certificates: hxxps://support.microsoft.com/en-us/topic/windows-secure-boot-certificate-expiration-and-ca-updates-7ff40d33-95dc-4c3c-8725-a9b95457578e
- Microsoft Secure Launch documentation: hxxps://learn.microsoft.com/windows/security/hardware-security/system-guard-secure-launch-and-smm-protection
- Microsoft VSM documentation: hxxps://learn.microsoft.com/virtualization/hyper-v-on-windows/tlfs/vsm