Patch tracker / KB5120249

KB5120249: Windows Server 2022 Security Update (August 2026)

KB5120249 is a High security update for Windows Server 2022, released 2026-08-11. It closes 161 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. The most likely of them to be attacked is CVE-2026-42976, which FIRST.org rates at 54% probability of exploitation in the next 30 days.

Update summary

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

Fixes 161 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 8.8 (High). EPSS exploit probability up to 6.2%. Among the top half of tracked Microsoft updates by EPSS exploit probability.

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-08-24
Changes tracked
6

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

The strongest signal is the steady upward drift in coverage for KB5120249. On 2026-08-12 the count moved from 159 to 160 fixed CVEs, then on 2026-08-20 it rose again from 160 to 161. This gradual, one-step-at-a-time expansion suggests ongoing patch maintenance, so review the latest state today and apply the current update.

  • 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-08-26). 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 the article, Find your ...

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

What the press says about this update

Trusted-source coverage of the CVEs this update fixes, pulled live from their own feeds.

“CVE-2026-68820 is in KEV. Here Is What CISA BOD 26-04 Actually Requires Now” Qualys, 2026-08-18
“Patch Tuesday - August 2026” Rapid7, 2026-08-11
“Microsoft's August 2026 Patch Tuesday addresses 398 CVEs (CVE-2026-68820)” Tenable, 2026-08-11
“The August 2026 Security Update Review” Zero Day Initiative, 2026-08-11

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.
Provided as is, without warranty; verify against the vendor advisory before acting. Data notice and terms.