Windows 11 26H2: security updates (KB) and vulnerabilities
1 KB updates fix 6 tracked CVEs for Windows 11 26H2.
Windows 11 26H2 has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 6. Most recent: 2026-10-13. Highest priority: CVE-2026-85790 (score 44/100).
- CVE-2026-85790 MEDIUM 5.9 UPGRADE UPGRADE Use after free in Microsoft QUIC allows an unauthorized attacker to disclose information over a network.
- CVE-2026-69452 HIGH 7.1 UPGRADE UPGRADE Use after free in Windows Enterprise App Management allows an authorized attacker to elevate privileges over a
- CVE-2026-96913 HIGH 8.8 UPGRADE UPGRADE Heap-based buffer overflow in Windows Kernel allows an authorized attacker to elevate privileges locally.
- CVE-2026-96911 HIGH 7.8 UPGRADE UPGRADE Improper link resolution before file access ('link following') in Microsoft Windows Search Component allows an
- CVE-2026-68836 HIGH 7.8 UPGRADE UPGRADE Heap-based buffer overflow in Windows kernel32.dll allows an authorized attacker to elevate privileges locally
- CVE-2026-96912 HIGH 7.8 UPGRADE UPGRADE Use after free in Windows Client License Service allows an authorized attacker to elevate privileges locally.
FAQ
How do I fix Windows 11 26H2 vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is Windows 11 26H2 being exploited right now?
None of the tracked Windows 11 26H2 CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which Windows 11 26H2 CVE should I patch first?
CVE-2026-85790 currently ranks highest (44/100): Use after free in Microsoft QUIC allows an unauthorized attacker to disclose information over a network..
Security updates (KB) for Windows 11 26H2
| KB | Fixed build | CVEs fixed | Newest CVE |
|---|---|---|---|
| KB5127648 | 10.0.26300.9711 | 6 | 2026-10-13 |
Install the KB from Windows Update, then verify with Get-HotFix -Id KBxxxxxxx or winver. Fixed build is the OS build number after the update.