cve.bz

CVE-2026-81963 (TrustedHive) Windows Update Stack Elevation of Privilege Vulnerability

7.8 highKEVEPSS 7.1%Fix available

Known as TrustedHive

High (7.8) in Microsoft Windows. In CISA KEV since 2026-09-08. EPSS 7.1% estimated probability of exploitation activity in the next 30 days.

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

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
7.1% (unchanged from 7.1% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 94th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-09-08, due 2026-09-22
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2026-09-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-59 Improper Link Resolution Before File Access (Link Following)
CWE-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
microsoft (CNA)
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-81963 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-81963?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-81963?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-81963 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows 11 version 23H2from 10.0.22631.0 before 10.0.22631.7582
Microsoft Windows 11 Version 23H2from 10.0.22631.0 before 10.0.22631.7582
Microsoft Windows 11 Version 24H2from 10.0.26100.0 before 10.0.26100.9445
Microsoft Windows 11 Version 25H2from 10.0.26200.0 before 10.0.26200.9445
Microsoft Windows 11 version 26H1from 10.0.28000.0 before 10.0.28000.2954
Microsoft Windows Server 2025from 10.0.26100.0 before 10.0.26100.33438
Microsoft Windows Server 2025 (Server Core installation)from 10.0.26100.0 before 10.0.26100.33438

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON