Skip to content
THREATWIRE
HighPoC AvailableKEV0-day

CVE-2026-81963

Windows Update Stack link following flaw lets a local user gain SYSTEM

A link following flaw in the Windows Update Stack lets a standard local user gain SYSTEM. Microsoft says it was exploited before the fix. Fixed on 8 September 2026 (Patch Tuesday). CVSS 3.1 7.8 (Important). In CISA KEV since 8 September. A third-party PoC appeared on 1 November; Microsoft has not confirmed it and ThreatWire has not verified it.

By ThreatWire Desk · Published 8 Sept 2026 · Updated 2 Nov 2026

CVSS
7.8
Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Class
LPE
Status
PoC Available
KEV
Listed in CISA KEV
0-day
Yes
Vendor
Microsoft
Products
Windows 11 23H2, Windows 11 24H2, Windows 11 25H2, Windows 11 26H1, Windows Server 2025, Windows Update Stack
Affected
Windows 11 23H2 before build 10.0.22631.7582, 24H2 before 10.0.26100.9445, 25H2 before 10.0.26200.9445 and 26H1 before 10.0.28000.2954, and Windows Server 2025 (including Server Core) before 10.0.26100.33438, on x64 and ARM64.
Fixed
September 2026 cumulative updates, released 8 September 2026: KB5122880 for Windows 11 23H2, KB5124008 for 24H2 and 25H2, KB5124012 for 26H1, and KB5122871 for Windows Server 2025. Later cumulative updates also include the fix.
Published
8 Sept 2026
Updated
2 Nov 2026

The status above is the claim. Links do not upgrade it.

CVE-2026-81963 is a link following flaw (CWE-59) in the Windows Update Stack. Microsoft also maps it to improper access control (CWE-284). A standard local user can elevate to SYSTEM.

Microsoft fixed it on 8 September 2026, in the September Patch Tuesday updates. It scores the flaw CVSS 3.1 7.8 and rates it Important. NVD has analyzed the record and shows the same score.

Exploited before the fix. Microsoft marks it "Exploitation Detected": exploited yes, publicly disclosed no. That makes it a zero-day at release. CISA's SSVC entry also lists exploitation as active.

CISA KEV: listed as "Microsoft Windows Link Following Vulnerability". Added on 8 September 2026, federal due date 22 September 2026. Known ransomware use: Unknown.

Attacker model: the attacker needs a local account first. It is not a remote flaw. It is useful as a second stage, after malware runs or a low-privilege session is stolen.

Fixed builds

The fix covers x64 and ARM64. Later cumulative updates also include it.

VersionUpdateFixed build
Windows 11 23H2KB512288010.0.22631.7582
Windows 11 24H2KB512400810.0.26100.9445
Windows 11 25H2KB512400810.0.26200.9445
Windows 11 26H1KB512401210.0.28000.2954
Windows Server 2025KB512287110.0.26100.33438

Windows Server 2025 Server Core uses the same update and build.

Credits

Microsoft credits haowei yan, Zhang WangJunJie of Hillstone Networks, Romain DEPERNE, and the Microsoft Threat Intelligence Center (MSTIC). Revisions 1.1 to 1.4 (latest 7 October 2026) only changed acknowledgements.

PoC note (2 November 2026)

A third-party GitHub repository was published on 1 November 2026. Its author suspects it matches this CVE. Microsoft has not confirmed that. ThreatWire has not run or verified it.

The author says they reported the issue to Microsoft in July. Microsoft closed it on 29 October as low severity, defense in depth, with no CVE. The author is not among Microsoft's credits.

The repository claims an arbitrary file write as SYSTEM from a standard user, through the servicing stack and link tricks. We do not reprint any steps. Our source-only review found nothing malicious in the source. Its prebuilt binaries are unverified. Do not run them outside an isolated lab. The PoC link field points to the repository.

Facts checked on 2 November 2026.

What to do: install the September 2026 or a later cumulative update. Check that each device reports the fixed build or higher. The KEV due date has long passed. Our explainer covers the details. Related Windows privilege-escalation: CVE-2026-85884.

Sources

Share on X@threatwire_https://www.threatwire.tech/cve/cve-2026-81963