CVE-2026-81963: Microsoft Windows Update Stack, is it exploitable where you run it
Code called: yesReached: openControl in front: noExploitation known: yesWalk it through the four questions
What the flaw is
CVE-2026-81963 is a link following flaw (CWE-59) in the Windows Update Stack. KEV also lists CWE-284. The stack resolves a file link improperly before it accesses a file, and Microsoft says an authorized local attacker can use that to gain SYSTEM privileges. No user interaction is needed.
The flaw is local only. The attacker must already run code on the host as a low-privileged user, so it is an escalation step and not initial access. The CVSS 3.1 base score is 7.8 (local, low complexity, low privileges, high impact on confidentiality, integrity and availability).
Are you exposed: each condition and how to check it
| Condition for exposure | How to check it on your system |
|---|---|
| the host runs Windows 11 23H2, 24H2, 25H2 or 26H1, or Windows Server 2025, below the fixed build for its release | Run winver, or in PowerShell [System.Environment]::OSVersion.Version, or cmd /c ver, and compare the full build and revision with the table. Get-HotFix -Id KB5124008 (use the KB from the table) also works, but a later cumulative update contains the fix, so compare builds when the KB is absent. |
| an attacker already runs code on the host as an authorized, low-privileged local user | This is a property of your environment (AV:L, PR:L). On a Windows 11 workstation every signed-in standard account is a local user, so the condition holds on every unpatched client. On Windows Server 2025 it depends on who can sign in: list them with net localgroup "Remote Desktop Users" and net localgroup Users, and review the Allow log on locally and Allow log on through Remote Desktop Services rights. Also consider any service or app on the host that runs untrusted code. |
Affected and fixed versions
Scroll the table sideways for more columns
| Windows release | Affected builds | First fixed build | Update (8 Sep 2026) |
|---|---|---|---|
| Windows 11 Version 23H2 (ARM64, x64) | Earlier than 10.0.22631.7582 | 10.0.22631.7582 | KB5122880 |
| Windows 11 Version 24H2 (ARM64, x64) | Earlier than 10.0.26100.9445 | 10.0.26100.9445 | KB5124008 |
| Windows 11 Version 25H2 (ARM64, x64) | Earlier than 10.0.26200.9445 | 10.0.26200.9445 | KB5124008 |
| Windows 11 Version 26H1 (ARM64, x64) | Earlier than 10.0.28000.2954 | 10.0.28000.2954 | KB5124012 |
| Windows Server 2025 (and Server Core) | Earlier than 10.0.26100.33438 | 10.0.26100.33438 | KB5122871 |
If the fix cannot go in yet
- Install the September 2026 cumulative update, or a later one, for the release (see the versions table). Cost: a restart. This is the fix.
- Microsoft lists no workaround. Two compensating controls reduce who can use the flaw. First, limit interactive and Remote Desktop logon to the accounts that need it, by removing groups from the Allow log on locally and Allow log on through Remote Desktop Services rights; cost: standard users and helpdesk staff lose access to those hosts. Second, enforce application control (WDAC or AppLocker) so that standard users cannot run unsigned or untrusted binaries; cost: a policy to build and maintain, and blocked tools until they are allowed.
What to look for
- Microsoft and CISA publish no indicator for this flaw, and CISA marks forensic triage as not required. Look for links that standard users create in folders the update stack reads or writes, such as C:\Windows\SoftwareDistribution and the servicing folders under C:\Windows. Sysmon does not log link creation as an event of its own, so search process creation (Sysmon event ID 1 or Security event 4688) for the commands that make links:
Get-WinEvent -FilterHashtable @{LogName='Microsoft-Windows-Sysmon/Operational'; Id=1} | Where-Object { $_.Message -match 'mklink\s+/[JD]|-ItemType\s+(Junction|SymbolicLink)' }. In Microsoft Defender for Endpoint the same filter isDeviceProcessEvents | where ProcessCommandLine matches regex @"mklink\s+/[JD]|-ItemType\s+(Junction|SymbolicLink)"with the account name excluding SYSTEM. To find links already in place, runGet-ChildItem C:\Windows\SoftwareDistribution -Recurse -Force -Attributes ReparsePointand inspect any result withfsutil reparsepoint query <path>. Microsoft has not said which paths this CVE uses, so treat any such link as a lead, not proof.
Exploited on the day of disclosure, 8 Sep 2026.
Exploitation reported so far
Microsoft marked the flaw as exploited on the day it published the fix, 8 Sep 2026, and CISA added it to KEV the same day. KEV lists ransomware campaign use as Unknown. Microsoft credits Zhang WangJunJie with Hillstone Networks, Romain Deperne, haowei yan and the Microsoft Threat Intelligence Center (MSTIC) as reporters. No attack details have been published.
Why attack-path analysis settles it
Exposure needs an unpatched Windows 11 or Server 2025 build and an attacker who already runs code locally on that host. The build check settles the first. As a local escalation step, an attack-path view of how an attacker reaches local code settles real priority, and KEV shows it is already used.
Related pages
Sources
- CVE-2026-81963: NVD record, read 19 Nov 2026
- CVE-2026-81963: CISA KEV entry (feed version 2026.11.18), read 19 Nov 2026
- CVE-2026-81963: Microsoft advisory (MSRC CVRF, September 2026 release: fixed builds, KBs, Exploited: Yes, revision history, acknowledgments), read 19 Nov 2026
- CVE-2026-81963: Microsoft advisory (MSRC API record), read 19 Nov 2026
Last reviewed 19 Nov 2026.