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

HighCISA KEV
2026-08-11
Released
160
CVEs fixed
8.8
Max CVSS v3
High
Severity
Deploy now
This update fixes vulnerabilities confirmed exploited in the wild.

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.

Senserva found thiswe track every release for this product line, so we can tell you this package is behind

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.

Senserva found thisread these before you deploy broadly

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

The full text, quoted from Microsoft

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.

Senserva Watchevery change we have recorded for this one
What changed, and when

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.

CVESeverityCVSSEPSSExploited
CVE-2026-68820High7.01.2%KEV
CVE-2026-59128Critical9.81.2%No
CVE-2026-59130Critical9.81.2%No
CVE-2026-59131Critical9.81.2%No
CVE-2026-59135Critical9.81.2%No
CVE-2026-59136Critical9.81.2%No
CVE-2026-59137Critical9.81.2%No
CVE-2026-59138Critical9.81.2%No
CVE-2026-61345Critical9.81.2%No
CVE-2026-61347Critical9.81.2%No
CVE-2026-61350Critical9.81.2%No
CVE-2026-61360Critical9.81.2%No
CVE-2026-61368Critical9.81.2%No
CVE-2026-61918Critical9.81.2%No
CVE-2026-61921Critical9.81.2%No
CVE-2026-61924Critical9.81.2%No
CVE-2026-61928Critical9.81.2%No
CVE-2026-61936Critical9.81.2%No
CVE-2026-62699Critical9.81.2%No
CVE-2026-62702Critical9.81.2%No
CVE-2026-62703Critical9.81.2%No
CVE-2026-62709Critical9.81.2%No
CVE-2026-62730Critical9.81.2%No
CVE-2026-62738Critical9.81.2%No
CVE-2026-62740Critical9.81.2%No
CVE-2026-62743Critical9.81.2%No
CVE-2026-62746Critical9.81.2%No
CVE-2026-62750Critical9.81.2%No
CVE-2026-62757Critical9.81.2%No
CVE-2026-62769Critical9.81.2%No
CVE-2026-62782Critical9.81.2%No
CVE-2026-62786Critical9.81.2%No
CVE-2026-62793Critical9.81.2%No
CVE-2026-62796Critical9.81.2%No
CVE-2026-62881Critical9.81.2%No
CVE-2026-62883Critical9.81.2%No
CVE-2026-62887Critical9.81.2%No
CVE-2026-65662Critical9.81.2%No
CVE-2026-65784Critical9.81.2%No
CVE-2026-65794Critical9.81.2%No
CVE-2026-65795Critical9.81.2%No
CVE-2026-65797Critical9.81.2%No
CVE-2026-65798Critical9.81.2%No
CVE-2026-65799Critical9.81.2%No
CVE-2026-6727Critical9.81.2%No
CVE-2026-70304Critical9.81.2%No
CVE-2026-70330Critical9.81.2%No
CVE-2026-49179High8.81.2%No
CVE-2026-62784High8.81.2%No
CVE-2026-62785High8.81.2%No
CVE-2026-62790High8.81.2%No
CVE-2026-62795High8.81.2%No
CVE-2026-62800High8.81.2%No
CVE-2026-62816High8.81.2%No
CVE-2026-62822High8.81.2%No
CVE-2026-62781High8.11.2%No
CVE-2026-62792High8.11.2%No
CVE-2026-62819High8.11.2%No
CVE-2026-62889High8.11.2%No
CVE-2026-6726High7.91.2%No
CVE-2026-42976High7.81.2%No
CVE-2026-54984High7.81.2%No
CVE-2026-56174High7.81.2%No
CVE-2026-59127High7.81.2%No
CVE-2026-61349High7.81.2%No
CVE-2026-61353High7.81.2%No
CVE-2026-61355High7.81.2%No
CVE-2026-61356High7.81.2%No
CVE-2026-61358High7.81.2%No
CVE-2026-61364High7.81.2%No
CVE-2026-61365High7.81.2%No
CVE-2026-61367High7.81.2%No
CVE-2026-61923High7.81.2%No
CVE-2026-61925High7.81.2%No
CVE-2026-61926High7.81.2%No
CVE-2026-61930High7.81.2%No
CVE-2026-61932High7.81.2%No
CVE-2026-61937High7.81.2%No
CVE-2026-62692High7.81.2%No
CVE-2026-62696High7.81.2%No
CVE-2026-62698High7.81.2%No
CVE-2026-62700High7.81.2%No
CVE-2026-62701High7.81.2%No
CVE-2026-62707High7.81.2%No
CVE-2026-62710High7.81.2%No
CVE-2026-62711High7.81.2%No
CVE-2026-62712High7.81.2%No
CVE-2026-62713High7.81.2%No
CVE-2026-62717High7.81.2%No
CVE-2026-62719High7.81.2%No
CVE-2026-62721High7.81.2%No
CVE-2026-62732High7.81.2%No
CVE-2026-62733High7.81.2%No
CVE-2026-62735High7.81.2%No
CVE-2026-62739High7.81.2%No
CVE-2026-62741High7.81.2%No
CVE-2026-62747High7.81.2%No
CVE-2026-62751High7.81.2%No
CVE-2026-62752High7.81.2%No
CVE-2026-62754High7.81.2%No
CVE-2026-62755High7.81.2%No
CVE-2026-62758High7.81.2%No
CVE-2026-62768High7.81.2%No
CVE-2026-62770High7.81.2%No
CVE-2026-62771High7.81.2%No
CVE-2026-62777High7.81.2%No
CVE-2026-62783High7.81.2%No
CVE-2026-62797High7.81.2%No
CVE-2026-62832High7.81.2%No
CVE-2026-62876High7.81.2%No
CVE-2026-62877High7.81.2%No
CVE-2026-62880High7.81.2%No
CVE-2026-62885High7.81.2%No
CVE-2026-62888High7.81.2%No
CVE-2026-62890High7.81.2%No
CVE-2026-62894High7.81.2%No
CVE-2026-65671High7.81.2%No
CVE-2026-65773High7.81.2%No
CVE-2026-65774High7.81.2%No
CVE-2026-65775High7.81.2%No
CVE-2026-65786High7.81.2%No
CVE-2026-65787High7.81.2%No
CVE-2026-65790High7.81.2%No
CVE-2026-65814High7.81.2%No
CVE-2026-66799High7.81.2%No
CVE-2026-66804High7.81.2%No
CVE-2026-70344High7.81.2%No
CVE-2026-70345High7.81.2%No
CVE-2026-70346High7.81.2%No
CVE-2026-70347High7.81.2%No
CVE-2026-54113High7.51.2%No
CVE-2026-59132High7.51.2%No
CVE-2026-59134High7.51.2%No
CVE-2026-61352High7.51.2%No
CVE-2026-61363High7.51.2%No
CVE-2026-50472High7.01.2%No
CVE-2026-59122High7.01.2%No
CVE-2026-59125High7.01.2%No
CVE-2026-59126High7.01.2%No
CVE-2026-61346High7.01.2%No
CVE-2026-61348High7.01.2%No
CVE-2026-61366High7.01.2%No
CVE-2026-61939High7.01.2%No
CVE-2026-62690High7.01.2%No
CVE-2026-62723High7.01.2%No
CVE-2026-62724High7.01.2%No
CVE-2026-62725High7.01.2%No
CVE-2026-62726High7.01.2%No
CVE-2026-62727High7.01.2%No
CVE-2026-62728High7.01.2%No
CVE-2026-62729High7.01.2%No
CVE-2026-62734High7.01.2%No
CVE-2026-62748High7.01.2%No
CVE-2026-62753High7.01.2%No
CVE-2026-62773High7.01.2%No
CVE-2026-62774High7.01.2%No
CVE-2026-62892High7.01.2%No
CVE-2026-62908High7.01.2%No
CVE-2026-65678High7.01.2%No
CVE-2026-70307High7.01.2%No

See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
All information provided as is, without warranty; verify against the vendor advisory before acting. All information and usage is subject to the Senserva EULA. Data notice and terms.