Patch tracker / KB5120228
KB5120228: Windows Server 2019 Security Update (August 2026)
KB5120228 is a Critical security update for Windows Server 2019, released 2026-08-11. It closes 212 CVEs with a maximum CVSS of 9.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
Fixes 212 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 9.8 (Critical). This update fixes an actively-exploited (CISA KEV) vulnerability.
Microsoft documents 1 known issue with this update.
- Windows Server Update Services (WSUS) does not display error details
Senserva AI Opinion and rich prompt for KB5120228
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5120228
- Released
- 2026-08-11
- Last changed
- 2026-08-11
- Changes tracked
- 2
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.
Check if KB5120228 is installed
Elevated PowerShell. No output means it is not installed.
Known issues, from Microsoft
Quoted from Microsoft's support article for KB5120228 (checked 2026-08-11). Verify against the article before acting.
Windows Server Update Services (WSUS) does not display error details
After installing KB5070893 or later updates, Windows Server Update Services (WSUS) does not display synchronization error details within its error reporting. This functionality is temporarily removed to address the Remote Code Execution Vulnerability, CVE-2025-59287 .
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 | Critical | 9.8 | - | KEV |
| CVE-2026-42976 | Critical | 9.8 | 54% | No |
| CVE-2026-49179 | Critical | 9.8 | - | No |
| CVE-2026-50472 | Critical | 9.8 | - | No |
| CVE-2026-54113 | Critical | 9.8 | - | No |
| CVE-2026-54984 | Critical | 9.8 | - | No |
| CVE-2026-56174 | Critical | 9.8 | - | No |
| CVE-2026-56179 | Critical | 9.8 | - | No |
| CVE-2026-59122 | Critical | 9.8 | - | No |
| CVE-2026-59125 | Critical | 9.8 | - | No |
| CVE-2026-59126 | Critical | 9.8 | - | No |
| CVE-2026-59127 | Critical | 9.8 | - | No |
| CVE-2026-59128 | Critical | 9.8 | - | No |
| CVE-2026-59130 | Critical | 9.8 | - | No |
| CVE-2026-59131 | Critical | 9.8 | - | No |
| CVE-2026-59132 | Critical | 9.8 | - | No |
| CVE-2026-59134 | Critical | 9.8 | - | No |
| CVE-2026-59135 | Critical | 9.8 | - | No |
| CVE-2026-59136 | Critical | 9.8 | - | No |
| CVE-2026-59137 | Critical | 9.8 | - | No |
| CVE-2026-59138 | Critical | 9.8 | - | No |
| CVE-2026-61345 | Critical | 9.8 | - | No |
| CVE-2026-61346 | Critical | 9.8 | - | No |
| CVE-2026-61347 | Critical | 9.8 | - | No |
| CVE-2026-61348 | Critical | 9.8 | - | No |
| CVE-2026-61349 | Critical | 9.8 | - | No |
| CVE-2026-61350 | Critical | 9.8 | - | No |
| CVE-2026-61352 | Critical | 9.8 | - | No |
| CVE-2026-61353 | Critical | 9.8 | - | No |
| CVE-2026-61355 | Critical | 9.8 | - | No |
| CVE-2026-61356 | Critical | 9.8 | - | No |
| CVE-2026-61357 | Critical | 9.8 | - | No |
| CVE-2026-61358 | Critical | 9.8 | - | No |
| CVE-2026-61359 | Critical | 9.8 | - | No |
| CVE-2026-61360 | Critical | 9.8 | - | No |
| CVE-2026-61361 | Critical | 9.8 | - | No |
| CVE-2026-61363 | Critical | 9.8 | - | No |
| CVE-2026-61364 | Critical | 9.8 | - | No |
| CVE-2026-61365 | Critical | 9.8 | - | No |
| CVE-2026-61366 | Critical | 9.8 | - | No |
| CVE-2026-61367 | Critical | 9.8 | - | No |
| CVE-2026-61368 | Critical | 9.8 | - | No |
| CVE-2026-61918 | Critical | 9.8 | - | No |
| CVE-2026-61920 | Critical | 9.8 | - | No |
| CVE-2026-61921 | Critical | 9.8 | - | No |
| CVE-2026-61923 | Critical | 9.8 | - | No |
| CVE-2026-61924 | Critical | 9.8 | - | No |
| CVE-2026-61925 | Critical | 9.8 | - | No |
| CVE-2026-61926 | Critical | 9.8 | - | No |
| CVE-2026-61927 | Critical | 9.8 | - | No |
| CVE-2026-61928 | Critical | 9.8 | - | No |
| CVE-2026-61929 | Critical | 9.8 | - | No |
| CVE-2026-61930 | Critical | 9.8 | - | No |
| CVE-2026-61933 | Critical | 9.8 | - | No |
| CVE-2026-61934 | Critical | 9.8 | - | No |
| CVE-2026-61936 | Critical | 9.8 | - | No |
| CVE-2026-61937 | Critical | 9.8 | - | No |
| CVE-2026-61938 | Critical | 9.8 | - | No |
| CVE-2026-61939 | Critical | 9.8 | - | No |
| CVE-2026-62690 | Critical | 9.8 | - | No |
| CVE-2026-62692 | Critical | 9.8 | - | No |
| CVE-2026-62695 | Critical | 9.8 | - | No |
| CVE-2026-62696 | Critical | 9.8 | - | No |
| CVE-2026-62698 | Critical | 9.8 | - | No |
| CVE-2026-62699 | Critical | 9.8 | - | No |
| CVE-2026-62700 | Critical | 9.8 | - | No |
| CVE-2026-62701 | Critical | 9.8 | - | No |
| CVE-2026-62702 | Critical | 9.8 | - | No |
| CVE-2026-62703 | Critical | 9.8 | - | No |
| CVE-2026-62707 | Critical | 9.8 | - | No |
| CVE-2026-62708 | Critical | 9.8 | - | No |
| CVE-2026-62709 | Critical | 9.8 | - | No |
| CVE-2026-62710 | Critical | 9.8 | - | No |
| CVE-2026-62711 | Critical | 9.8 | - | No |
| CVE-2026-62712 | Critical | 9.8 | - | No |
| CVE-2026-62713 | Critical | 9.8 | - | No |
| CVE-2026-62714 | Critical | 9.8 | - | No |
| CVE-2026-62715 | Critical | 9.8 | - | No |
| CVE-2026-62716 | Critical | 9.8 | - | No |
| CVE-2026-62717 | Critical | 9.8 | - | No |
| CVE-2026-62718 | Critical | 9.8 | - | No |
| CVE-2026-62719 | Critical | 9.8 | - | No |
| CVE-2026-62720 | Critical | 9.8 | - | No |
| CVE-2026-62721 | Critical | 9.8 | - | No |
| CVE-2026-62722 | Critical | 9.8 | - | No |
| CVE-2026-62723 | Critical | 9.8 | - | No |
| CVE-2026-62724 | Critical | 9.8 | - | No |
| CVE-2026-62725 | Critical | 9.8 | - | No |
| CVE-2026-62726 | Critical | 9.8 | - | No |
| CVE-2026-62728 | Critical | 9.8 | - | No |
| CVE-2026-62729 | Critical | 9.8 | - | No |
| CVE-2026-62730 | Critical | 9.8 | - | No |
| CVE-2026-62732 | Critical | 9.8 | - | No |
| CVE-2026-62733 | Critical | 9.8 | - | No |
| CVE-2026-62734 | Critical | 9.8 | - | No |
| CVE-2026-62735 | Critical | 9.8 | - | No |
| CVE-2026-62736 | Critical | 9.8 | - | No |
| CVE-2026-62737 | Critical | 9.8 | - | No |
| CVE-2026-62738 | Critical | 9.8 | - | No |
| CVE-2026-62739 | Critical | 9.8 | - | No |
| CVE-2026-62740 | Critical | 9.8 | - | No |
| CVE-2026-62741 | Critical | 9.8 | - | No |
| CVE-2026-62742 | Critical | 9.8 | - | No |
| CVE-2026-62743 | Critical | 9.8 | - | No |
| CVE-2026-62745 | Critical | 9.8 | - | No |
| CVE-2026-62746 | Critical | 9.8 | - | No |
| CVE-2026-62747 | Critical | 9.8 | - | No |
| CVE-2026-62748 | Critical | 9.8 | - | No |
| CVE-2026-62749 | Critical | 9.8 | - | No |
| CVE-2026-62750 | Critical | 9.8 | - | No |
| CVE-2026-62751 | Critical | 9.8 | - | No |
| CVE-2026-62752 | Critical | 9.8 | - | No |
| CVE-2026-62753 | Critical | 9.8 | - | No |
| CVE-2026-62755 | Critical | 9.8 | - | No |
| CVE-2026-62757 | Critical | 9.8 | - | No |
| CVE-2026-62758 | Critical | 9.8 | - | No |
| CVE-2026-62761 | Critical | 9.8 | - | No |
| CVE-2026-62766 | Critical | 9.8 | - | No |
| CVE-2026-62768 | Critical | 9.8 | - | No |
| CVE-2026-62769 | Critical | 9.8 | - | No |
| CVE-2026-62770 | Critical | 9.8 | - | No |
| CVE-2026-62771 | Critical | 9.8 | - | No |
| CVE-2026-62773 | Critical | 9.8 | - | No |
| CVE-2026-62774 | Critical | 9.8 | - | No |
| CVE-2026-62776 | Critical | 9.8 | - | No |
| CVE-2026-62777 | Critical | 9.8 | - | No |
| CVE-2026-62778 | Critical | 9.8 | - | No |
| CVE-2026-62779 | Critical | 9.8 | - | No |
| CVE-2026-62780 | Critical | 9.8 | - | No |
| CVE-2026-62781 | Critical | 9.8 | - | No |
| CVE-2026-62782 | Critical | 9.8 | - | No |
| CVE-2026-62783 | Critical | 9.8 | - | No |
| CVE-2026-62784 | Critical | 9.8 | - | No |
| CVE-2026-62785 | Critical | 9.8 | - | No |
| CVE-2026-62786 | Critical | 9.8 | - | No |
| CVE-2026-62787 | Critical | 9.8 | - | No |
| CVE-2026-62788 | Critical | 9.8 | - | No |
| CVE-2026-62790 | Critical | 9.8 | - | No |
| CVE-2026-62792 | Critical | 9.8 | - | No |
| CVE-2026-62793 | Critical | 9.8 | - | No |
| CVE-2026-62795 | Critical | 9.8 | - | No |
| CVE-2026-62796 | Critical | 9.8 | - | No |
| CVE-2026-62797 | Critical | 9.8 | - | No |
| CVE-2026-62798 | Critical | 9.8 | - | No |
| CVE-2026-62800 | Critical | 9.8 | - | No |
| CVE-2026-62803 | Critical | 9.8 | - | No |
| CVE-2026-62807 | Critical | 9.8 | - | No |
| CVE-2026-62811 | Critical | 9.8 | - | No |
| CVE-2026-62812 | Critical | 9.8 | - | No |
| CVE-2026-62814 | Critical | 9.8 | - | No |
| CVE-2026-62815 | Critical | 9.8 | - | No |
| CVE-2026-62816 | Critical | 9.8 | - | No |
| CVE-2026-62817 | Critical | 9.8 | - | No |
| CVE-2026-62818 | Critical | 9.8 | - | No |
| CVE-2026-62819 | Critical | 9.8 | - | No |
| CVE-2026-62820 | Critical | 9.8 | - | No |
| CVE-2026-62822 | Critical | 9.8 | - | No |
| CVE-2026-62823 | Critical | 9.8 | - | No |
| CVE-2026-62832 | Critical | 9.8 | - | No |
| CVE-2026-62876 | Critical | 9.8 | - | No |
| CVE-2026-62877 | Critical | 9.8 | - | No |
| CVE-2026-62878 | Critical | 9.8 | - | No |
| CVE-2026-62880 | Critical | 9.8 | - | No |
| CVE-2026-62881 | Critical | 9.8 | - | No |
| CVE-2026-62883 | Critical | 9.8 | - | No |
| CVE-2026-62885 | Critical | 9.8 | - | No |
| CVE-2026-62887 | Critical | 9.8 | - | No |
| CVE-2026-62888 | Critical | 9.8 | - | No |
| CVE-2026-62889 | Critical | 9.8 | - | No |
| CVE-2026-62890 | Critical | 9.8 | - | No |
| CVE-2026-62892 | Critical | 9.8 | - | No |
| CVE-2026-62893 | Critical | 9.8 | - | No |
| CVE-2026-62894 | Critical | 9.8 | - | No |
| CVE-2026-62908 | Critical | 9.8 | - | No |
| CVE-2026-65662 | Critical | 9.8 | - | No |
| CVE-2026-65671 | Critical | 9.8 | - | No |
| CVE-2026-65672 | Critical | 9.8 | - | No |
| CVE-2026-65678 | Critical | 9.8 | - | No |
| CVE-2026-65679 | Critical | 9.8 | - | No |
| CVE-2026-65681 | Critical | 9.8 | - | No |
| CVE-2026-65773 | Critical | 9.8 | - | No |
| CVE-2026-65774 | Critical | 9.8 | - | No |
| CVE-2026-65775 | Critical | 9.8 | - | No |
| CVE-2026-65776 | Critical | 9.8 | - | No |
| CVE-2026-65777 | Critical | 9.8 | - | No |
| CVE-2026-65784 | Critical | 9.8 | - | No |
| CVE-2026-65785 | Critical | 9.8 | - | No |
| CVE-2026-65786 | Critical | 9.8 | - | No |
| CVE-2026-65787 | Critical | 9.8 | - | No |
| CVE-2026-65788 | Critical | 9.8 | - | No |
| CVE-2026-65789 | Critical | 9.8 | - | No |
| CVE-2026-65790 | Critical | 9.8 | - | No |
| CVE-2026-65791 | Critical | 9.8 | - | No |
| CVE-2026-65794 | Critical | 9.8 | - | No |
| CVE-2026-65795 | Critical | 9.8 | - | No |
| CVE-2026-65796 | Critical | 9.8 | - | No |
| CVE-2026-65797 | Critical | 9.8 | - | No |
| CVE-2026-65798 | Critical | 9.8 | - | No |
| CVE-2026-65799 | Critical | 9.8 | - | No |
| CVE-2026-65814 | Critical | 9.8 | - | No |
| CVE-2026-66799 | Critical | 9.8 | - | No |
| CVE-2026-66802 | Critical | 9.8 | - | No |
| CVE-2026-6726 | Critical | 9.8 | - | No |
| CVE-2026-6727 | Critical | 9.8 | - | No |
| CVE-2026-68819 | Critical | 9.8 | - | No |
| CVE-2026-70304 | Critical | 9.8 | - | No |
| CVE-2026-70307 | Critical | 9.8 | - | No |
| CVE-2026-70330 | Critical | 9.8 | - | No |
| CVE-2026-70344 | Critical | 9.8 | - | No |
| CVE-2026-70345 | Critical | 9.8 | - | No |
| CVE-2026-70346 | Critical | 9.8 | - | No |
| CVE-2026-70347 | Critical | 9.8 | - | No |
What the press says about this update
Trusted-source coverage of the CVEs this update fixes, pulled live from their own feeds.
Scope and sources
- Affected products
- Also released in August 2026
KB5002882
39 CVEs · Critical · exploitedKB5002883
40 CVEs · Critical · exploitedKB5002891
40 CVEs · Critical · exploitedKB5120229
194 CVEs · Critical · exploitedKB5120233
213 CVEs · Critical · exploitedKB5120238
181 CVEs · Critical · exploitedKB5120240
170 CVEs · Critical · exploitedKB5120242
194 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.