Patch tracker / KB5121000
KB5121000: Windows 11 version 26H1 Security Update (August 2026)
KB5121000 is a Critical security update for Windows 11 version 26H1, released 2026-08-11. It closes 195 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. It is the third largest of the 65 updates Microsoft shipped that month, by CVEs closed.
Update summary
Fixes 195 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 9.8 (Critical). 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 11 version 26H1 for x64-based Systems has shipped since this one: KB5124012 (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.
- Microsoft Teams and Outlook might fail to launch on ARM-based devices
Senserva AI Opinion and rich prompt for KB5121000
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5121000
- Released
- 2026-08-11
- Last changed
- 2026-09-26
- Changes tracked
- 10
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 KB5121000 on 2026-08-20: CVEs fixed 197 to 198.
- 2026-08-12 CVEs fixed 196 to 197
- 2026-08-20 CVEs fixed 197 to 198
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 KB5121000 is installed
Elevated PowerShell. No output means it is not installed.
Known issues, from Microsoft
Quoted from Microsoft's support article for KB5121000 (checked 2026-10-10). Verify against the article before acting.
Microsoft Teams and Outlook might fail to launch on ARM-based devices
Symptoms
After installing Windows security updates released on or after August 11, 2026, (KB5121000) , Microsoft Teams and the new Outlook for Windows might fail to launch or might close unexpectedly on ARM-based devices, such as Surface Pro 11 and Surface Laptop 7. Classic Outlook, Word, Excel, and other applications are not known to be affected. This issue is most likely to occur on new or freshly imaged PCs that have not yet installed any Microsoft Store updates.
Workaround
To work around this issue:
Open Microsoft Store.
Select Downloads > Check for updates.
Install the latest update for the Auto Super Resolution Package (version 1.0.19.0 or later).
Resolution
This issue is resolved in Windows updates released on and after September 8, 2026 such as KB5124012 . We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
Windows release health for this update
From Microsoft's Windows release health for Windows 11, version 26H1, checked 2026-10-12. Microsoft's issue text is linked from each title.
Issues Microsoft traces to this update
- Microsoft Teams and Outlook might fail to launch on ARM-based devices
Resolved by KB5124012. Microsoft last updated it 2026-09-08 11:37 PT.
Other open issues on these Windows versions
- USB audio devices might fail to start or produce no sound
Mitigated. Microsoft last updated it 2026-09-29 10:12 PT. - Devices might experience a black screen or desktop loading issues after sign-in
Mitigated. Microsoft last updated it 2026-09-29 10:12 PT.
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-61933 | 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-62708 | 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-62775 | 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-62798 | Critical | 9.8 | 1.2% | No |
| CVE-2026-62815 | 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-65777 | Critical | 9.8 | 1.2% | No |
| CVE-2026-65784 | Critical | 9.8 | 1.2% | No |
| CVE-2026-65785 | 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-70348 | Critical | 9.8 | 1.2% | No |
| CVE-2026-72971 | 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-56179 | High | 8.3 | 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-66802 | 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-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-61357 | High | 7.8 | 1.2% | No |
| CVE-2026-61358 | High | 7.8 | 1.2% | No |
| CVE-2026-61359 | 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-61934 | High | 7.8 | 1.2% | No |
| CVE-2026-61937 | High | 7.8 | 1.2% | No |
| CVE-2026-62688 | High | 7.8 | 1.2% | No |
| CVE-2026-62692 | High | 7.8 | 1.2% | No |
| CVE-2026-62695 | 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-62722 | 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-62736 | High | 7.8 | 1.2% | No |
| CVE-2026-62737 | 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-62772 | High | 7.8 | 1.2% | No |
| CVE-2026-62777 | High | 7.8 | 1.2% | No |
| CVE-2026-62779 | 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-62799 | High | 7.8 | 1.2% | No |
| CVE-2026-62811 | 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-65672 | 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-61361 | High | 7.0 | 1.2% | No |
| CVE-2026-61366 | High | 7.0 | 1.2% | No |
| CVE-2026-61927 | High | 7.0 | 1.2% | No |
| CVE-2026-61929 | High | 7.0 | 1.2% | No |
| CVE-2026-61938 | 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-62693 | High | 7.0 | 1.2% | No |
| CVE-2026-62705 | 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-62749 | High | 7.0 | 1.2% | No |
| CVE-2026-62753 | High | 7.0 | 1.2% | No |
| CVE-2026-62766 | 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-62780 | High | 7.0 | 1.2% | No |
| CVE-2026-62788 | 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-65776 | High | 7.0 | 1.2% | No |
| CVE-2026-65779 | High | 7.0 | 1.2% | No |
| CVE-2026-65780 | High | 7.0 | 1.2% | No |
| CVE-2026-65788 | 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.