What is CVE-2026-81963?

CVE-2026-81963 is Windows Update Stack Elevation of Privilege Vulnerability. The supplied enrichment data classifies it as Path Traversal mapped to CWE-59 Link Following; CWE-284 Improper Access Control.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

5 public PoC repositories reported; 1 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with Not reported where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-81963 using CVSS 7.8, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVhighPath Traversalpublic exploit

CVE-2026-81963

CVE-2026-81963 — Windows Update Stack Elevation of Privilege Vulnerability

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2026-81963 in CISA KEV with 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.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Improper link resolution before file access ('link following') in Windows Update Stack allows an authorized attacker to elevate privileges locally.

Published Sep 8, 2026Updated Sep 8, 2026Sources: NVD, Microsoft (CNA), CISA, GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Sep 8, 2026

EPSS

ahead of 0% of scored CVEs

Affects

Microsoft

7 products listed

CVSS base

7.8

high · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade Windows 11 version 23H2 to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA 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.

Federal deadline Sep 22, 2026 — in 12 days

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Microsoft	Windows 11 version 23H2	10.0.22631.0 to < 10.0.22631.7582	Vulnerable
Microsoft	Windows 11 Version 23H2	10.0.22631.0 to < 10.0.22631.7582	Vulnerable
Microsoft	Windows 11 Version 24H2	10.0.26100.0 to < 10.0.26100.9445	Vulnerable
Microsoft	Windows 11 Version 25H2	10.0.26200.0 to < 10.0.26200.9445	Vulnerable
Microsoft	Windows 11 version 26H1	10.0.28000.0 to < 10.0.28000.2954	Vulnerable
Microsoft	Windows Server 2025	10.0.26100.0 to < 10.0.26100.33438	Vulnerable
Microsoft	Windows Server 2025 (Server Core installation)	10.0.26100.0 to < 10.0.26100.33438	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Local

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.8	CVSS 3.1	high	1.8	5.9	Microsoft (CNA), GHSA
7.8	CVSS 3.1	high	—	—	Microsoft (CNA)

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

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

Read Files or Directories
Modify Files or Directories
Bypass Protection Mechanism
Execute Unauthorized Code or Commands

Mitigation: Follow the principle of least privilege when assigning access rights to entities in a software system. Denying access to a file can prevent an attacker from replacing that file with a link to a sensitive file. Ensure good compartmentalization in the system to provide protected areas that can be trusted.::

CWE-284 · Improper Access Control

Varies by Context::

Mitigation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.

Weakness & attack patterns

CWE-59Link Following
CWE-284Improper Access Control

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-132 · Symlink AttackCAPEC-17 · Using Malicious FilesCAPEC-76 · Manipulating Web Input to File System CallsCAPEC-35 · Leverage Executable Code in Non-Executable Files

T1547.009Boot or Logon Autostart Execution: Shortcut Modification
T1574.005Hijack Execution Flow: Executable Installer File Permissions Weakness
T1574.010Hijack Execution Flow: Services File Permissions Weakness

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Sep 8, 2026

Federal deadline

Sep 22, 2026

in 12 days

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1 of the 5 sampled are weaponized

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

2 more posts on this CVEShowing 5 of 7 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Monitor for scanner or exploit-pattern traffic after 5 public PoC repositories were reported.

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added to CISA KEV catalog
Sep 8, 2026 · CISA
Added · CVSS 3.1 7.8 (AV:L)
Sep 8, 2026 · NVD
Initial · CVE published
Sep 8, 2026 · NVD
Added · GHSA-4j4j-2wjq-mxqj published (high)
Sep 8, 2026 · GitHub Security Advisory
CVE published by MITRE.
Sep 8, 2026 · SOCRadar CTI

Source activity

Readings a source repeats on a schedule, counted rather than listed.

1×CVE modified by NIST: CISA KEV details updated.Sep 8, 2026 · SOCRadar CTI

References

7 on the record

msrc.microsoft.com/update-guide/vulnerability/CVE-2026-81963
Patch, Vendor Advisory, Mitre, NIST
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-81963
US Government Resource, NIST
nvd.nist.gov/vuln/detail/CVE-2026-81963
NVD, Vendor Advisory
github.com/advisories/GHSA-4j4j-2wjq-mxqj
Exploit, Third Party Advisory
msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2026-81963
Vendor Advisory
www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
US Government Resource
www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
US Government Resource

Coverage

5 stories from the feeds we poll

Elsewhere on this site

Microsoftevery CVE for this vendor
September 2026what else CISA listed
Path Traversalsame class
CWE-59other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-81963 is Windows Update Stack Elevation of Privilege Vulnerability, a high vulnerability affecting Windows 11 version 23H2, Windows 11 Version 23H2, Windows 11 Version 24H2, Windows 11 Version 25H2, Windows 11 version 26H1, Windows Server 2025, Windows Server 2025 (Server Core installation) from Microsoft. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 5 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.8 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.