CVE-2026-81963Microsoft Windows Link Following Vulnerability
CVE-2026-81963 is a link following in Microsoft Windows, rated high (7.8 on CVSS 3.1).
Why this priority: Exploited in the wild: listed in CISA's KEV catalog.
Published · Updated · NVD status: Analyzed
What it is
The software follows a symbolic link an attacker planted, so it reads or writes a file other than the one it checked. Access to a resource or action is not restricted to the people meant to have it.
How it is reached
An attacker can exploit it by someone who can already run code or sign in on the machine, with an ordinary user account, and nobody has to click anything.
What an attacker gains
A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker read or write files outside the folders the service meant to expose.
Is it being exploited?
CISA added it to the Known Exploited Vulnerabilities catalog on 2026-09-08: it is being exploited in the wild. EPSS estimates a 0.39% chance of exploitation activity in the next 30 days, higher than 34% of scored CVEs.
What to do
- Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2026-09-22.
- Apply the update for your edition of Microsoft Windows. Fixed builds: Windows 11 Version 23H2: 10.0.22631.7582; Windows 11 Version 24H2: 10.0.26100.9445; Windows 11 Version 25H2: 10.0.26200.9445; Windows 11 version 26H1: 10.0.28000.2954; Windows Server 2025: 10.0.26100.33438; Windows Server 2025 (Server Core installation): 10.0.26100.33438. The patch notes are linked below.
- Limit who can run code or sign in on the hosts that run it.
- Check exposed instances for signs of compromise, not only for the version.
Description from NVD
Improper link resolution before file access ('link following') in Windows Update Stack allows an authorized attacker to elevate privileges locally.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Operating systems on servers, workstations or devices. Everything on the host inherits the flaw.
- File storage the service can read or write. The flaw sits between the application and the file system it can reach.
- Permission checks in APIs and admin surfaces. The flaw sits between one role or tenant and another.
- Multi-tenant services. The flaw sits between one role or tenant and another.
Trust boundaries in play
- Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
- Between the application and the file system it can reach. An attacker who crosses it can read or write files outside the folders the service meant to expose.
- Between one role or tenant and another. An attacker who crosses it can reach data or actions their role should not allow.
Questions to answer about your own systems
- Where does Microsoft Windows run in your systems, and at which version?
- Which of those hosts also run code or users you do not fully trust?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.