Patch tracker / KB5120249
KB5120249: Windows 10 Version 21H2 Security Update (August 2026)
KB5120249 is a High security update for Windows 10 Version 21H2, released 2026-08-11. It closes 160 CVEs with a maximum CVSS of 8.8. At least one of them is actively exploited (CISA KEV), so this is a deploy-first update. It is the 11th largest of the 65 updates Microsoft shipped that month, by CVEs closed.
Update summary
Fixes 160 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 8.8 (High). EPSS exploit probability up to 1.2%. Among the lower half of tracked Microsoft updates by EPSS exploit probability.
A newer security update for Windows 10 Version 21H2 for ARM64-based Systems has shipped since this one: KB5122878 (2026-09-08). For cumulative update families the newer package includes these fixes, so installing that one is usually the shorter path. Verify against your own update rings before you skip this package.
Microsoft documents 1 known issue with this update.
- Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key
Senserva AI Opinion and rich prompt for KB5120249
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5120249
- Released
- 2026-08-11
- Last changed
- 2026-09-24
- Changes tracked
- 8
Senserva began recording day-to-day change history on 2026-07-07, and refreshes it several times a day. Release dates are historical where Microsoft publishes them; revision history is tracked from that date forward, so it does not include changes made before then.
Microsoft revised KB5120249 on 2026-08-20: CVEs fixed 160 to 161.
- 2026-08-12 CVEs fixed 159 to 160
- 2026-08-20 CVEs fixed 160 to 161
Recorded by Senserva on the dates shown, from the MSRC release feed. This is what moved and when, which neither the vendor advisory nor NVD publishes.
Check if KB5120249 is installed
Elevated PowerShell. No output means it is not installed.
Known issues, from Microsoft
Quoted from Microsoft's support article for KB5120249 (checked 2026-10-10). Verify against the article before acting.
Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key
Symptoms
Some devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key on the first restart after installing this update.
This issue only affects a limited number of systems in which ALL the following conditions are true. These conditions are unlikely to be found on personal devices not managed by IT departments.
BitLocker is enabled on the OS drive.
The Group Policy Configure TPM platform validation profile for native UEFI firmware configurations is configured, and PCR7 is included in the validation profile (or the equivalent registry key is set manually).
System Information (msinfo32.exe) reports Secure Boot State PCR7 Binding as Not Possible .
The Windows UEFI CA 2023 certificate is present in the device’s Secure Boot Signature Database (DB), making the device eligible for the 2023‑signed Windows Boot Manager to be made the default.
The device is not already running the 2023-signed Windows Boot Manager.
In this scenario, the BitLocker recovery key only needs to be entered once -- subsequent restarts will not trigger a BitLocker recovery screen, as long as the group policy configuration remains unchanged. For help finding your BitLocker recovery key, see [Find your BitLocker recovery key](https://support.microsoft.com/Windows/Security/Encryption/find-your-bitlocker-recovery-key).
Enterprises are recommended to audit their BitLocker group policies for explicit PCR7 inclusion and check msinfo32.exe for their PCR7 binding status before installing this update.
Resolution
This issue is addressed in update KB5122878 . After installing update KB5122878, devices with this incompatible group policy configuration are prevented from installing the 2023-signed Windows Boot Manager. If your device was impacted, Event ID 1032 will appear in the System event log when installing Windows updates: "The Secure Boot update Boot Manager (2023) was not applied due to a known incompatibility with the current BitLocker configuration."
If you receive Event ID 1032 , Microsoft strongly recommends removing the Group Policy configuration before installing updates so that you can install the 2023-signed Windows Boot Manager and continue to receive the latest Secure Boot protection.
Remove the Group Policy configuration before installing the update (Recommended)
Open Group Policy Editor (gpedit.msc) or your Group Policy Management Console.
Navigate to: Computer Configuration > Administrative ...
CVEs fixed by this update
Sorted exploited-first, then by CVSS. Every CVE links to its Senserva page with the full risk facts, references, and a ready-to-paste AI prompt.
| CVE | Severity | CVSS | EPSS | Exploited |
|---|---|---|---|---|
| CVE-2026-68820 | High | 7.0 | 1.2% | KEV |
| CVE-2026-59128 | Critical | 9.8 | 1.2% | No |
| CVE-2026-59130 | Critical | 9.8 | 1.2% | No |
| CVE-2026-59131 | Critical | 9.8 | 1.2% | No |
| CVE-2026-59135 | Critical | 9.8 | 1.2% | No |
| CVE-2026-59136 | Critical | 9.8 | 1.2% | No |
| CVE-2026-59137 | Critical | 9.8 | 1.2% | No |
| CVE-2026-59138 | Critical | 9.8 | 1.2% | No |
| CVE-2026-61345 | Critical | 9.8 | 1.2% | No |
| CVE-2026-61347 | Critical | 9.8 | 1.2% | No |
| CVE-2026-61350 | Critical | 9.8 | 1.2% | No |
| CVE-2026-61360 | Critical | 9.8 | 1.2% | No |
| CVE-2026-61368 | Critical | 9.8 | 1.2% | No |
| CVE-2026-61918 | Critical | 9.8 | 1.2% | No |
| CVE-2026-61921 | Critical | 9.8 | 1.2% | No |
| CVE-2026-61924 | Critical | 9.8 | 1.2% | No |
| CVE-2026-61928 | Critical | 9.8 | 1.2% | No |
| CVE-2026-61936 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62699 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62702 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62703 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62709 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62730 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62738 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62740 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62743 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62746 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62750 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62757 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62769 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62782 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62786 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62793 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62796 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62881 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62883 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62887 | Critical | 9.8 | 1.2% | No |
| CVE-2026-65662 | Critical | 9.8 | 1.2% | No |
| CVE-2026-65784 | Critical | 9.8 | 1.2% | No |
| CVE-2026-65794 | Critical | 9.8 | 1.2% | No |
| CVE-2026-65795 | Critical | 9.8 | 1.2% | No |
| CVE-2026-65797 | Critical | 9.8 | 1.2% | No |
| CVE-2026-65798 | Critical | 9.8 | 1.2% | No |
| CVE-2026-65799 | Critical | 9.8 | 1.2% | No |
| CVE-2026-6727 | Critical | 9.8 | 1.2% | No |
| CVE-2026-70304 | Critical | 9.8 | 1.2% | No |
| CVE-2026-70330 | Critical | 9.8 | 1.2% | No |
| CVE-2026-49179 | High | 8.8 | 1.2% | No |
| CVE-2026-62784 | High | 8.8 | 1.2% | No |
| CVE-2026-62785 | High | 8.8 | 1.2% | No |
| CVE-2026-62790 | High | 8.8 | 1.2% | No |
| CVE-2026-62795 | High | 8.8 | 1.2% | No |
| CVE-2026-62800 | High | 8.8 | 1.2% | No |
| CVE-2026-62816 | High | 8.8 | 1.2% | No |
| CVE-2026-62822 | High | 8.8 | 1.2% | No |
| CVE-2026-62781 | High | 8.1 | 1.2% | No |
| CVE-2026-62792 | High | 8.1 | 1.2% | No |
| CVE-2026-62819 | High | 8.1 | 1.2% | No |
| CVE-2026-62889 | High | 8.1 | 1.2% | No |
| CVE-2026-6726 | High | 7.9 | 1.2% | No |
| CVE-2026-42976 | High | 7.8 | 1.2% | No |
| CVE-2026-54984 | High | 7.8 | 1.2% | No |
| CVE-2026-56174 | High | 7.8 | 1.2% | No |
| CVE-2026-59127 | High | 7.8 | 1.2% | No |
| CVE-2026-61349 | High | 7.8 | 1.2% | No |
| CVE-2026-61353 | High | 7.8 | 1.2% | No |
| CVE-2026-61355 | High | 7.8 | 1.2% | No |
| CVE-2026-61356 | High | 7.8 | 1.2% | No |
| CVE-2026-61358 | High | 7.8 | 1.2% | No |
| CVE-2026-61364 | High | 7.8 | 1.2% | No |
| CVE-2026-61365 | High | 7.8 | 1.2% | No |
| CVE-2026-61367 | High | 7.8 | 1.2% | No |
| CVE-2026-61923 | High | 7.8 | 1.2% | No |
| CVE-2026-61925 | High | 7.8 | 1.2% | No |
| CVE-2026-61926 | High | 7.8 | 1.2% | No |
| CVE-2026-61930 | High | 7.8 | 1.2% | No |
| CVE-2026-61932 | High | 7.8 | 1.2% | No |
| CVE-2026-61937 | High | 7.8 | 1.2% | No |
| CVE-2026-62692 | High | 7.8 | 1.2% | No |
| CVE-2026-62696 | High | 7.8 | 1.2% | No |
| CVE-2026-62698 | High | 7.8 | 1.2% | No |
| CVE-2026-62700 | High | 7.8 | 1.2% | No |
| CVE-2026-62701 | High | 7.8 | 1.2% | No |
| CVE-2026-62707 | High | 7.8 | 1.2% | No |
| CVE-2026-62710 | High | 7.8 | 1.2% | No |
| CVE-2026-62711 | High | 7.8 | 1.2% | No |
| CVE-2026-62712 | High | 7.8 | 1.2% | No |
| CVE-2026-62713 | High | 7.8 | 1.2% | No |
| CVE-2026-62717 | High | 7.8 | 1.2% | No |
| CVE-2026-62719 | High | 7.8 | 1.2% | No |
| CVE-2026-62721 | High | 7.8 | 1.2% | No |
| CVE-2026-62732 | High | 7.8 | 1.2% | No |
| CVE-2026-62733 | High | 7.8 | 1.2% | No |
| CVE-2026-62735 | High | 7.8 | 1.2% | No |
| CVE-2026-62739 | High | 7.8 | 1.2% | No |
| CVE-2026-62741 | High | 7.8 | 1.2% | No |
| CVE-2026-62747 | High | 7.8 | 1.2% | No |
| CVE-2026-62751 | High | 7.8 | 1.2% | No |
| CVE-2026-62752 | High | 7.8 | 1.2% | No |
| CVE-2026-62754 | High | 7.8 | 1.2% | No |
| CVE-2026-62755 | High | 7.8 | 1.2% | No |
| CVE-2026-62758 | High | 7.8 | 1.2% | No |
| CVE-2026-62768 | High | 7.8 | 1.2% | No |
| CVE-2026-62770 | High | 7.8 | 1.2% | No |
| CVE-2026-62771 | High | 7.8 | 1.2% | No |
| CVE-2026-62777 | High | 7.8 | 1.2% | No |
| CVE-2026-62783 | High | 7.8 | 1.2% | No |
| CVE-2026-62797 | High | 7.8 | 1.2% | No |
| CVE-2026-62832 | High | 7.8 | 1.2% | No |
| CVE-2026-62876 | High | 7.8 | 1.2% | No |
| CVE-2026-62877 | High | 7.8 | 1.2% | No |
| CVE-2026-62880 | High | 7.8 | 1.2% | No |
| CVE-2026-62885 | High | 7.8 | 1.2% | No |
| CVE-2026-62888 | High | 7.8 | 1.2% | No |
| CVE-2026-62890 | High | 7.8 | 1.2% | No |
| CVE-2026-62894 | High | 7.8 | 1.2% | No |
| CVE-2026-65671 | High | 7.8 | 1.2% | No |
| CVE-2026-65773 | High | 7.8 | 1.2% | No |
| CVE-2026-65774 | High | 7.8 | 1.2% | No |
| CVE-2026-65775 | High | 7.8 | 1.2% | No |
| CVE-2026-65786 | High | 7.8 | 1.2% | No |
| CVE-2026-65787 | High | 7.8 | 1.2% | No |
| CVE-2026-65790 | High | 7.8 | 1.2% | No |
| CVE-2026-65814 | High | 7.8 | 1.2% | No |
| CVE-2026-66799 | High | 7.8 | 1.2% | No |
| CVE-2026-66804 | High | 7.8 | 1.2% | No |
| CVE-2026-70344 | High | 7.8 | 1.2% | No |
| CVE-2026-70345 | High | 7.8 | 1.2% | No |
| CVE-2026-70346 | High | 7.8 | 1.2% | No |
| CVE-2026-70347 | High | 7.8 | 1.2% | No |
| CVE-2026-54113 | High | 7.5 | 1.2% | No |
| CVE-2026-59132 | High | 7.5 | 1.2% | No |
| CVE-2026-59134 | High | 7.5 | 1.2% | No |
| CVE-2026-61352 | High | 7.5 | 1.2% | No |
| CVE-2026-61363 | High | 7.5 | 1.2% | No |
| CVE-2026-50472 | High | 7.0 | 1.2% | No |
| CVE-2026-59122 | High | 7.0 | 1.2% | No |
| CVE-2026-59125 | High | 7.0 | 1.2% | No |
| CVE-2026-59126 | High | 7.0 | 1.2% | No |
| CVE-2026-61346 | High | 7.0 | 1.2% | No |
| CVE-2026-61348 | High | 7.0 | 1.2% | No |
| CVE-2026-61366 | High | 7.0 | 1.2% | No |
| CVE-2026-61939 | High | 7.0 | 1.2% | No |
| CVE-2026-62690 | High | 7.0 | 1.2% | No |
| CVE-2026-62723 | High | 7.0 | 1.2% | No |
| CVE-2026-62724 | High | 7.0 | 1.2% | No |
| CVE-2026-62725 | High | 7.0 | 1.2% | No |
| CVE-2026-62726 | High | 7.0 | 1.2% | No |
| CVE-2026-62727 | High | 7.0 | 1.2% | No |
| CVE-2026-62728 | High | 7.0 | 1.2% | No |
| CVE-2026-62729 | High | 7.0 | 1.2% | No |
| CVE-2026-62734 | High | 7.0 | 1.2% | No |
| CVE-2026-62748 | High | 7.0 | 1.2% | No |
| CVE-2026-62753 | High | 7.0 | 1.2% | No |
| CVE-2026-62773 | High | 7.0 | 1.2% | No |
| CVE-2026-62774 | High | 7.0 | 1.2% | No |
| CVE-2026-62892 | High | 7.0 | 1.2% | No |
| CVE-2026-62908 | High | 7.0 | 1.2% | No |
| CVE-2026-65678 | High | 7.0 | 1.2% | No |
| CVE-2026-70307 | High | 7.0 | 1.2% | No |
Scope and sources
- Affected products
- Also released in August 2026
KB5120228
215 CVEs · Critical · exploitedKB5120229
195 CVEs · Critical · exploitedKB5120233
215 CVEs · Critical · exploitedKB5120238
183 CVEs · Critical · exploitedKB5120240
170 CVEs · Critical · exploitedKB5120242
195 CVEs · Critical · exploitedKB5120385
144 CVEs · Critical · exploitedKB5120386
139 CVEs · Critical · exploitedThe full month, summarized: Microsoft Patch Tuesday.
- Authoritative references
See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.