Patch tracker / KB5126868
KB5126868: Windows Server 2016 Security Update (October 2026)
KB5126868 is a Critical security update for Windows Server 2016, released 2026-10-13. It closes 769 CVEs with a maximum CVSS of 9.8. At least one of them is actively exploited (CISA KEV), so it is urgent, and Microsoft lists 2 known issues: test it before broad deployment. The most likely of them to be attacked is CVE-2026-96951, which FIRST.org rates at 10% probability of exploitation in the next 30 days.
Before you deploy: Microsoft lists 2 known issues for this update.
Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.
Update summary
Fixes 769 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 9.8 (Critical). EPSS exploit probability up to 9.8%. Among the top half of tracked Microsoft updates by EPSS exploit probability.
Microsoft documents 2 known issues with this update.
- Users might be unable to sign in to OWA or send emails on Exchange Server
- USB Audio Class 1.0 devices with error Code 10 or no output
Senserva AI Opinion and rich prompt for KB5126868
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5126868
- Released
- 2026-10-13
- Last changed
- 2026-10-25
- 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.
Microsoft revised KB5126868 on 2026-10-16: CVEs fixed 768 to 769.
- 2026-10-15 CVEs fixed 767 to 768
- 2026-10-16 CVEs fixed 768 to 769
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 KB5126868 is installed
Elevated PowerShell. No output means it is not installed.
Known issues, from Microsoft
Quoted from Microsoft's support article for KB5126868 (checked 2026-11-03). Microsoft lists 2 known issues. Verify against the article before acting.
1. Users might be unable to sign in to OWA or send emails on Exchange Server
Symptoms:
After installing this update, some on-premises Exchange servers might experience issues accessing or sending email. Users might be unable to sign in to Outlook on the web (OWA), or email messages sent from Outlook might remain in the Outbox and not be delivered. Additionally, Exchange might experience issues accessing mailboxes during mailbox replication.
In some affected configurations, Exchange Server OWA might fail with an error MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142) with Event ID 1006 logged in the application log. Another reported symptom is growing email queues. Installing the October 2026 Exchange server security updates isn’t required for these issues to occur.
Workaround
This issue can be temporarily mitigated by modifying the registry key as described in Exchange servers may become unstable after installation of October 2026 Windows updates .
The October 2026 update introduced a default limit on the amount of memory used by Endpoint Mapper when handling Endpoint Lookup calls.
For workloads such as Exchange Server, the default limit of 512 simultaneous Endpoint Lookup calls might not be sufficient under heavy load. Administrators can use this registry setting to increase the maximum number of simultaneous Endpoint Lookup calls, which increases the amount of memory that Endpoint Mapper can use.
Microsoft Support: An additional mitigation is available for affected devices through Microsoft Support. To apply this mitigation in your organization, please contact Microsoft Support for business .
Next steps: Microsoft investigating this issue and will provide more information when it is available.
2. USB Audio Class 1.0 devices with error Code 10 or no output
Symptoms
After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms:
The device displays an error in Device Manager: "This device cannot start (Code 10).”
No audio output.
Volume controls are unresponsive or remain at zero.
Sound settings are unresponsive or unavailable.
Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode.
This issue is limited to USB Audio Class 1.0 devices.
Resolution
This issue is partially resolved in the out-of-band (OOB) update released on September 14, 2026. This OOB update resolves the symptoms experienced on devices using 8-channel or 3D audio modes. Microsoft is working to address the other symptoms and will provide more information when it is available.
IT administrators who need an immediate workaround for the symptoms not addressed yet by the OOB update should contact Microsoft Support for Business for assistance.
Windows release health for this update
From Microsoft's Windows release health for Windows Server 2016 and Windows 10, version 1607, checked 2026-11-03. Microsoft's issue text is linked from each title.
Issues Microsoft traces to this update
- Users might be unable to sign in to OWA or send emails on Exchange Server
Mitigated. Microsoft last updated it 2026-10-16 21:48 PT.
From the Senserva blog
- Will This Patch Break Something? Read Past Known Issues
October 17, 2026 · Mark Shavlik - Patch and Vulnerability Intelligence
July 10, 2026 · Kyle, Senserva Dev Team
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.
Scope and sources
- Affected products
- Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 version 1607
- Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2016
- Windows 10 Version 1607 for 32-bit Systems
- Windows 10 Version 1607 for x64-based Systems
- Windows Server 2016
- Windows Server 2016 (Server Core installation)
- Also released in October 2026
KB5126646
1041 CVEs · Critical · exploitedKB5126651
918 CVEs · Critical · exploitedKB5126653
965 CVEs · Critical · exploitedKB5126655
977 CVEs · Critical · exploitedKB5126657
899 CVEs · Critical · exploitedKB5126836
649 CVEs · Critical · exploitedKB5127646
997 CVEs · Critical · exploitedKB5127648
1009 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.