CVE-2026-81963

HIGH(7.8)KEV

Microsoft Windows Link Following Vulnerability

Description

CVE-2026-81963 is a high-severity link following vulnerability in the Windows Update Stack that allows an authorized local attacker to elevate privileges. The flaw is an improper link resolution before file access: a privileged Windows Update component follows a symbolic link or junction that a low-privileged user can create, and performs its file operation on the attacker-chosen target instead of the intended path. Any user who can already run code on the machine — including a standard domain user or a compromised low-privilege service — can use this Windows vulnerability to reach SYSTEM-level control of the host. CVE-2026-81963 carries a CVSS score of 7.8 and is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog with a remediation deadline of 22 September 2026.

KEV Information

Vendor
Microsoft
Product
Windows
Date Added
September 8, 2026
Due Date
September 22, 2026
Required Action
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

CVSS Score

Vector String
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HOpen in Calculator
Attack Vector
LOCAL
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
Exploitability Score
1.8
Impact Score
5.9

CWEs

Affected Products

VendorProductVersion
microsoftwindows 11 23h2< 10.0.22631.7582
microsoftwindows 11 24h2< 10.0.26100.9445
microsoftwindows 11 25h2< 10.0.26200.9445
microsoftwindows 11 26h1< 10.0.28000.2954
microsoftwindows server 2025< 10.0.26100.33438

References

Weakness Type

CWE-59: Improper Link Resolution Before File Access ('Link Following')

Link following occurs when software accesses a file through a path that an attacker can redirect by creating or manipulating symbolic links, junctions or hard links, so the privileged process operates on a target of the attacker's choosing. In CVE-2026-81963 the Windows Update Stack resolves a path in a location a low-privileged user can write, and the link planted there redirects the privileged file operation to a sensitive system location.

Learn more: CWE-59 — Improper Link Resolution Before File Access ('Link Following')

CWE-284: Improper Access Control

Improper access control is the broader failure to properly restrict access to a resource from an unauthorized actor. Here it describes the outcome of the link following: an authorized but low-privileged user ends up directing operations that should be restricted to the update service, crossing a privilege boundary the operating system is supposed to enforce.

Learn more: CWE-284 — Improper Access Control

Impact Analysis

CVE-2026-81963 requires local access and low privileges, so it is not directly reachable from the internet — an attacker must already be able to execute code on the machine, whether as a logged-in standard user, through a phishing payload, or via a separate remote vulnerability. From that starting point the attack has low complexity and needs no user interaction, and the result is high impact to confidentiality, integrity and availability: successful elevation typically yields SYSTEM privileges, allowing the attacker to read any data on the host, install persistence, disable security tooling and control the machine entirely. That makes CVE-2026-81963 a classic second-stage vulnerability — the step that converts an initial foothold into full host compromise and, in a domain environment, into credential theft that enables lateral movement. The CVSS 3.1 base score is 7.8 (High) and the EPSS score of roughly 0.6% (48th percentile) reflects that local elevation bugs are not mass-scanned, but CISA's KEV listing confirms real-world use in attack chains.

Exploit Maturity

CISA has confirmed active exploitation of CVE-2026-81963 by adding it to the Known Exploited Vulnerabilities catalog with a 22 September 2026 remediation deadline, so this Windows Update Stack flaw is being used in real attack chains rather than only demonstrated in research. No public exploit code is listed among the available references, and Microsoft's MSRC entry is the only vendor source, which is typical for elevation-of-privilege bugs used by targeted intrusion sets before broad proof-of-concept release. The EPSS score of about 0.6% (48th percentile) is expected to be low for a local elevation vulnerability, because EPSS models internet-facing scanning activity that simply does not apply to a bug requiring prior code execution — it should not be read as a sign of low risk. Treat CVE-2026-81963 as the privilege-escalation half of an intrusion chain and patch it on the same urgency as the remote vulnerabilities that would deliver the initial foothold.

Remediation

  1. Follow the CISA KEV required action. Apply mitigations in accordance with Microsoft's instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV due date is 22 September 2026.
  2. Install the Microsoft security update from MSRC CVE-2026-81963. Fixed builds are Windows 11 23H2 10.0.22631.7582, Windows 11 24H2 10.0.26100.9445, Windows 11 25H2 10.0.26200.9445, Windows 11 26H1 10.0.28000.2954 and Windows Server 2025 10.0.26100.33438 — verify the resulting build number rather than only confirming the update installed.
  3. Prioritise multi-user and shared systems. Terminal servers, VDI hosts, jump servers and developer workstations where non-administrative users run code are the highest-value targets for a local elevation flaw, so patch those ahead of single-user endpoints.
  4. Reduce the ability to plant links and monitor for abuse. Ensure standard users cannot create symbolic links by keeping the "Create symbolic links" privilege restricted to administrators, audit writable directories used by privileged services, and alert on junction or symlink creation in system-writable paths and on unexpected SYSTEM-level process creation from user contexts via EDR telemetry.
  5. Harden long term by applying least privilege so that users and services run without unnecessary rights, centralising access control decisions, and — as the general defence against link following — ensuring privileged code never opens a path in a directory writable by untrusted users without verifying that the path does not traverse a link, preferring file-descriptor-based operations that cannot be redirected after the check.

Technical Details

CVE-2026-81963 is an improper link resolution before file access (CWE-59) leading to improper access control (CWE-284) in the Windows Update Stack. A privileged component of the update stack performs a file operation on a path located in a directory that a low-privileged user can influence; the attacker plants a symbolic link, junction or hard link at that path before the privileged operation runs, and because the component resolves the path without verifying that it does not traverse a link, the write, delete or permission change lands on a target the attacker selected. Redirecting a privileged file operation into a protected system location is the standard route to arbitrary file write as SYSTEM, which converts into code execution at that privilege level. The CVSS vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H records the attack as local, low complexity, requiring low privileges and no user interaction, with full compromise of confidentiality, integrity and availability at unchanged scope. Many link-following elevations depend on winning a timing window between the path check and the file access, which is why patching rather than mitigation is the reliable fix.

Frequently Asked Questions

Is CVE-2026-81963 being actively exploited?

Yes. CISA added CVE-2026-81963 to its Known Exploited Vulnerabilities catalog with a remediation due date of 22 September 2026, confirming exploitation in the wild. Its low EPSS score is expected for a local elevation-of-privilege flaw and does not indicate low risk, since such bugs are used after an attacker already has code execution.

What products are affected by CVE-2026-81963?

Windows 11 23H2, 24H2, 25H2 and 26H1 and Windows Server 2025 are affected, with fixes in builds 10.0.22631.7582, 10.0.26100.9445, 10.0.26200.9445, 10.0.28000.2954 and 10.0.26100.33438 respectively. The vulnerable component is the Windows Update Stack, which is present on all these systems by default.

How do I fix CVE-2026-81963?

Install the Microsoft security update referenced in the MSRC advisory for CVE-2026-81963 and confirm the resulting OS build number matches or exceeds the fixed build for your Windows version. Prioritise multi-user systems such as terminal servers and VDI hosts, and restrict the ability of standard users to create symbolic links.

How severe is CVE-2026-81963?

CVE-2026-81963 is rated High with a CVSS 3.1 base score of 7.8. It requires local access and low privileges rather than being remotely exploitable, but needs no user interaction and results in high confidentiality, integrity and availability impact — typically full SYSTEM control of the host — which makes it a critical link in an attack chain despite the local attack vector.

CVSS Score

7.8
HIGH(7.8)

EPSS Score

EPSS Score7.12%
EPSS Percentile94.4%

Dates

PublishedSeptember 8, 2026
Last ModifiedSeptember 9, 2026
StatusAnalyzed
CVSS Versionv3.1

Need Help With Vulnerability Management?

Our security experts can help you prioritize and remediate vulnerabilities effectively.