# Windows 11 and Windows Server Patch Tuesday October 2026 (KB5127648, KB5126646, KB5126655): what changed

Source: https://srvscripts.com/guides/kb5127648-october-2026/
Updated: 2026-11-02
Publisher: srvScripts (https://srvscripts.com/)

The October 2026 Patch Tuesday (13 October) is the largest Microsoft has shipped: roughly 1,410 CVEs across Windows, Office, Exchange, SharePoint, .NET and Azure, with one Windows zero-day already exploited. For administrators the month matters less for the headline count than for two server-side changes that can break things on their own: Windows Server 2025 now enforces the NTLMv1 block by default, and the same update introduces a known issue on on-premises Exchange. This guide lists the KB numbers per branch, what changed, what to test before broad approval, and how to verify the install.

**Short answer:** KB5127648 is the October 2026 cumulative update for Windows 11 24H2, 25H2 and 26H2 (builds 26100.9711, 26200.9711 and 26300.9711); Windows 11 26H1 gets KB5127646 (28000.3231) and 23H2 gets KB5126653. Windows Server 2025 gets KB5126646 (26100.33650), Server 2022 KB5126655 (20348.5761), Server 2019 KB5126651 and Server 2016 KB5126868. Install it: CVE-2026-96951 (a Mark-of-the-Web bypass in Windows Shell) is exploited in the wild. Pilot it on Exchange servers and on anything that still speaks NTLMv1 or MS-CHAPv2 first. (Reviewed October 2026.)

In short: KB5127648 (Windows 11), KB5126646 (Server 2025) and KB5126655 (Server 2022) are the October 2026 cumulative updates; CVE-2026-96951 is exploited, and Server 2025 now enforces the NTLMv1 block.

## KB numbers by branch

| Product | KB | OS build | Bundled SSU |
| --- | --- | --- | --- |
| Windows 11 24H2 / 25H2 / 26H2 | KB5127648 | 26100.9711 / 26200.9711 / 26300.9711 | combined |
| Windows 11 26H1 | KB5127646 | 28000.3231 | combined |
| Windows 11 23H2 | KB5126653 | — | combined |
| Windows 10 22H2 (ESU only) | KB5126657 | — | combined |
| Windows Server 2025 | KB5126646 | 26100.33650 | KB5126645 (26100.33634) |
| Windows Server 2022 | KB5126655 | 20348.5761 | KB5126654 (20348.5739) |
| Windows Server 2019 | KB5126651 | — | — |
| Windows Server 2016 | KB5126868 | — | KB5126649 |

October 2026 cumulative updates. Windows 11 25H2 and 26H2 receive the 24H2 package with no exclusive changes. Windows 10 22H2 only receives the update under Extended Security Updates.

Windows Server 2025 and Windows 11 24H2 share the 26100 code base but the server build number has drifted far ahead (26100.33650 versus 26100.9711); do not use one to judge the other. The server update needs the servicing stack update already present, so a Catalog download of KB5126646 on a machine that has not been patched since mid-2025 fails until the latest SSU is installed first.

## The security content

Published counts differ by a few entries depending on who is counting (1,407 to 1,413), with more than 70 rated Critical. Elevation of privilege makes up roughly half of the list and remote code execution about a fifth. Three issues were public or exploited before the patch:

- **CVE-2026-96951** — Windows Shell security feature bypass (Mark of the Web), CVSS 8.8, **exploited in the wild**. A crafted file opened from a download or attachment skips the SmartScreen/MotW warning. This is the one that justifies a short pilot and a fast rollout.

- **CVE-2026-108398** — .NET Framework security feature bypass (Windows Defender Application Control), CVSS 8.8, publicly disclosed, no known exploitation. Fixed by the October .NET Framework updates (KB5127690 on 24H2/25H2 and Server 2025, KB5127693 and KB5127687 on Server 2022), not by the Windows cumulative update.

- **CVE-2026-92707** — MessagePack-CSharp denial of service, CVSS 5.3, publicly disclosed. Only relevant where your own .NET applications bundle that library.

Server-facing Critical fixes worth reading before the change record: a Windows DHCP Server unauthenticated RCE (CVE-2026-96934, 9.8), a Message Queuing RCE (CVE-2026-100202, 9.8 — disable MSMQ where unused and keep TCP 1801 off the perimeter), two MsQuic RCEs (CVE-2026-100219 and CVE-2026-105016, 9.8) that affect HTTP/3 and SMB over QUIC, and a set of Outlook RCEs of which CVE-2026-70291 and CVE-2026-88156 trigger from the Preview Pane. Exchange Server Subscription Edition gets security update SU11 (KB5128895) the same day; SharePoint Subscription Edition gets KB5002927.

## What changed on Windows Server

Three behavioural changes in KB5126646 (Server 2025) and KB5126655 (Server 2022) deserve a test ring of their own:

- **NTLMv1 is now enforced on Server 2025.** When `BlockNtlmv1SSO` is not set and Credential Guard is off, the default moves from Audit to Enforce. Anything that still authenticates with NTLMv1 — most often Wi-Fi, Ethernet 802.1X and VPN connections using MS-CHAPv2 against NPS — stops working after the reboot. Server 2022 adds the NTLM auditing (who uses NTLM, why it was chosen, where) without the enforcement change, so use its logs to find the stragglers before the 2025 hosts go.

- **AD FS DKM ACL remediation is automatic.** Overly permissive ACLs on the DKM container (CVE-2026-56155) are fixed by default. If you have a reason to keep the old permissions, set `RemediateDkmAcl` to 0 before patching; otherwise expect the change and verify federation sign-in afterwards.

- **ReFS auditing on external storage** is on by default (enforcement off). Harmless in itself, but it adds events you will see on backup targets and SAN-attached ReFS volumes.

Smaller additions: quick machine recovery is now available on Server 2025 (off by default, Group Policy to enable), ML-KEM post-quantum key exchange for TLS 1.3, cURL 8.21.0, a Storage Spaces Direct fix for tiered virtual disks that stayed offline after an update, Netlogon secure-channel fixes for domain controllers created before Server 2025, and new time-zone data (permanent DST for British Columbia and Alberta from November 2026, a new Manitoba Standard Time zone).

## Known issues

- **Exchange Server on-premises (Server 2025 and 2022 hosts).** After the update some servers refuse Outlook on the web sign-ins, leave sent mail in the Outbox, show mailbox replication problems and growing queues, and log `MapiExceptionMdbOffline` (ec=1142) with Event ID 1006. Microsoft attributes it to a new default limit of 512 simultaneous Endpoint Lookup calls and lists a registry mitigation, with a permanent fix still under investigation. Pilot on one Exchange host with a maintenance window, and keep the uninstall path ready.

- **WSUS** still hides synchronization error details (a side effect of the CVE-2025-59287 fix from late 2025). Sync failures look blank in the console; read `SoftwareDistribution.log` instead.

- **Windows 11 clients.** Microsoft lists no new client issues, but the USB Audio Class 1.0 problem (device fails to start or is silent) can persist on a small number of PCs. Administrators also report WPA2-Enterprise PEAP Wi-Fi failures after the update; treat that as the NTLMv1 enforcement above when the RADIUS server is Server 2025.

- **PC-to-PC Migration** has been removed from Windows Backup; it is a feature removal, not a bug.

## Stage the rollout

- **Day 0–2, workstations:** approve KB5127648 / KB5127646 for a pilot ring that includes one machine behind Smart App Control and one that connects to corporate Wi-Fi with 802.1X. The exploited CVE is a client-side bypass, so clients should not wait a full week.

- **Day 0–2, servers:** before approving KB5126646, turn on NTLM auditing on your Server 2022 domain controllers and NPS servers, or read the Event ID 4624 logon events for `LmPackageName = NTLM V1`. Anything that shows up must move to NTLMv2, PEAP-MSCHAPv2 with Credential Guard considered, or EAP-TLS.

- **Exchange:** one host first, in a window, with the registry mitigation from the KB article at hand. Install SU11 (KB5128895) in the same window so you do not reboot twice.

- **Broad ring:** the rest after 3–5 quiet days. In WSUS, approve the Windows update and the matching .NET Framework update together — the WDAC bypass is only closed by the .NET package.

## Install and verify on a single machine

```
# Windows 11 24H2/25H2/26H2
Get-HotFix -Id KB5127648
# Windows Server 2025 / 2022
Get-HotFix -Id KB5126646, KB5126655
# build check (expect 26100.9711 / 26200.9711 / 26300.9711 / 28000.3231 on clients, 26100.33650 or 20348.5761 on servers)
Get-ComputerInfo | Select-Object OsName, OsVersion, OsBuildNumber
(Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion").UBR
DISM /Online /Get-Packages | findstr /i "KB5127648 KB5126646 KB5126655"
```

Offline install from the Microsoft Update Catalog (install the SSU first on servers that are more than a few months behind):

```
Add-WindowsPackage -Online -PackagePath "C:\Updates\windows11.0-kb5126645-x64.msu"   # SSU, Server 2025 only if required
Add-WindowsPackage -Online -PackagePath "C:\Updates\windows11.0-kb5126646-x64.msu"   # LCU
Restart-Computer
```

To check whether NTLMv1 is still in use on a domain controller or NPS server before the enforcement lands:

```
Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4624} -MaxEvents 5000 |
  Where-Object { $_.Message -match 'LmPackageName:\s+NTLM V1' } |
  Select-Object TimeCreated, @{n='Account';e={($_.Message -split "`n" | Select-String 'Account Name:')[1]}}, @{n='Source';e={($_.Message | Select-String 'Source Network Address:\s+(\S+)').Matches.Groups[1].Value}} |
  Format-Table -AutoSize
```

If the update fails with 0x800f0922 or 0x80073712, repair the component store first; see [Windows Update error 0x800f0922, 0x80070002 and 0x80073712](/guides/windows-update-error-0x800f0922/) and [DISM RestoreHealth with an offline source](/guides/dism-restorehealth-offline-source/). Machines that cannot take a reboot in the window can use [Windows Server 2025 hotpatching](/guides/windows-server-2025-hotpatch/) for the next baseline instead.

## Roll back if you must

```
wusa /uninstall /kb:5126646 /quiet /norestart     # Server 2025
wusa /uninstall /kb:5127648 /quiet /norestart     # Windows 11 24H2/25H2/26H2
```

Removing the LCU does not remove the bundled servicing stack update, which is by design. For the Exchange issue, the registry mitigation in the KB article is the better option than a rollback because it keeps the month’s security fixes; for the NTLMv1 enforcement, setting `BlockNtlmv1SSO` explicitly to audit mode is a configuration change, not a rollback.

## KB5127648 at a glance

KB5127648: what this guide covers.

**Official documentation:** [KB5127648 release notes](https://support.microsoft.com/help/5127648), [KB5126646 (Windows Server 2025)](https://support.microsoft.com/help/5126646), [KB5126655 (Windows Server 2022)](https://support.microsoft.com/help/5126655), [Microsoft Security Update Guide](https://msrc.microsoft.com/update-guide/).

**Related guides:** [September 2026 Patch Tuesday (KB5124008) and the KB5129195 out-of-band fix](https://srvscripts.com/guides/kb5124008-september-2026/) · [Exchange Server SE upgrade from 2019 CU15](https://srvscripts.com/guides/exchange-server-se-upgrade/) · [Windows Server 2025 hotpatch setup](https://srvscripts.com/guides/windows-server-2025-hotpatch/).

## Frequently asked questions

### Which KB is the October 2026 Patch Tuesday update for Windows Server 2025?

KB5126646, OS build 26100.33650, released 13 October 2026, with servicing stack update KB5126645 bundled. Windows Server 2022 gets KB5126655 (20348.5761), Server 2019 KB5126651 and Server 2016 KB5126868.

### Does KB5127648 apply to Windows 11 25H2 and 26H2 as well as 24H2?

Yes. Windows 11 24H2, 25H2 and 26H2 share the same package, KB5127648, and reach builds 26100.9711, 26200.9711 and 26300.9711. Windows 11 26H1 is a different branch and gets KB5127646 (build 28000.3231); 23H2 gets KB5126653.

### Why did Wi-Fi or VPN authentication break after installing KB5126646?

Windows Server 2025 now enforces the NTLMv1 block by default when BlockNtlmv1SSO is unset and Credential Guard is disabled. MS-CHAPv2 (PEAP) connections authenticated by an NPS server on that host fail. Move clients to EAP-TLS or NTLMv2-capable paths, or set BlockNtlmv1SSO to audit mode while you migrate.

### Is there a zero-day in the October 2026 update?

One exploited: CVE-2026-96951, a Mark-of-the-Web security feature bypass in Windows Shell (CVSS 8.8). Two more were publicly disclosed but not known to be exploited: CVE-2026-108398 in the .NET Framework (WDAC bypass, fixed by the October .NET updates) and CVE-2026-92707 in MessagePack-CSharp.
