Skip to content
PiLabs security advisory Updated 17 November 2026
High 7.8 CVE-2026-81963 Known exploited

Privilege escalation through link following in the Windows Update Stack of Microsoft Windows

Affected
Microsoft Windows
Affected versions
< 10.0.22631.7582; < 10.0.26100.9445; < 10.0.26100.33438; < 10.0.26200.9445; < 10.0.28000.2954
Disclosed
Last updated
CVSS 3.1 vector
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Written automatically on 17 November 2026 from the NVD and the CISA catalogue of known exploited vulnerabilities. The facts above come from those sources; check them before you act. Sources of this advisory

Sources describe a link following flaw in the Windows Update Stack that lets an authorized local attacker elevate privileges. CISA lists CVE-2026-81963 as exploited; the CVSS score is 7.8 (high).

What is affected

The flaw is tracked as CVE-2026-81963 and affects Microsoft Windows. The sources title it Microsoft Windows Link Following Vulnerability and place it in the Windows Update Stack. The affected version ranges, exactly as given in the sources, are:

  • < 10.0.22631.7582
  • < 10.0.26100.9445
  • < 10.0.26100.33438
  • < 10.0.26200.9445
  • < 10.0.28000.2954

Each entry means the versions before the number shown. The fixed releases are listed in the Microsoft advisory, not here.

What the flaw allows

The description in the sources states that improper link resolution before file access, known as link following, in the Windows Update Stack allows an authorized attacker to elevate privileges locally. In plain terms, a user who already has an account and local access to a system could gain higher privileges than intended.

The sources assign the weakness identifiers CWE-59 and CWE-284. The CVSS version 3.1 base score is 7.8, which is high severity. The vector describes an attack that is local, of low complexity, needs low privileges and no user interaction, and has a high impact on confidentiality, integrity and availability.

Exploitation

CISA lists this vulnerability in its CISA Known Exploited Vulnerabilities catalogue as exploited. CISA added it on 2026-09-08, the same date on which the vulnerability was disclosed. The due date of 2026-09-22 is CISA's stated deadline for US federal agencies to act. CISA records the use in ransomware campaigns as unknown. The sources do not describe how exploitation takes place, and this advisory does not either.

What to do

Because the flaw is listed as exploited, you should treat it as a priority. Compare the Windows build versions in your environment with the affected ranges above, and read the Microsoft security advisory, which lists the fixed releases and explains how to check your exposure. Further record details are in the NVD entry.

For US federal agencies, CISA's required action is to apply mitigations in line with vendor instructions, or to discontinue use of the product if mitigations are unavailable. Other organisations can use the same approach as a reference point for planning.

What to do

Apply the fixes that Microsoft lists in the Microsoft security advisory, starting with systems whose build is below the affected version ranges. The advisory names the fixed releases and explains how to check exposure. The facts name no workaround, so use the vendor instructions. CISA's stated deadline for US federal agencies is 2026-09-22.

Sources

All vulnerabilities

Need to know whether these vulnerabilities affect you?

A consultant can check which of the affected products you run and what to fix first. For a wider review, ask for a security assessment.