Windows Update Stack Elevation of Privilege Vulnerability
Why It Matters
Analysis dossierWhy It Matters
Improper link resolution before file access ('link following') in Windows Update Stack allows an authorized attacker to elevate privileges locally.
Immediate Attention
Yes
Unknown
Risk basis: Known exploitation signal from CISA KEV or ransomware metadata
Affected Products & Remediation
10 source-backed products- Windows Server 2025 (Server Core installation) · version range not provided by source · Microsoft MSRC · Source
- Windows 11 Version 25H2 for ARM64-based Systems · version range not provided by source · Microsoft MSRC · Source
- Windows 11 Version 25H2 for x64-based Systems · version range not provided by source · Microsoft MSRC · Source
- Windows 11 Version 23H2 for ARM64-based Systems · version range not provided by source · Microsoft MSRC · Source
- Windows 11 Version 23H2 for x64-based Systems · version range not provided by source · Microsoft MSRC · Source
- Windows 11 Version 24H2 for ARM64-based Systems · version range not provided by source · Microsoft MSRC · Source
- Windows 11 Version 24H2 for x64-based Systems · version range not provided by source · Microsoft MSRC · Source
- Windows Server 2025 · version range not provided by source · Microsoft MSRC · Source
- Windows 11 version 26H1 for x64-based Systems · version range not provided by source · Microsoft MSRC · Source
- Windows 11 Version 26H1 for ARM64-based Systems · version range not provided by source · Microsoft MSRC · Source
Vendor or catalog guidance (source)
- Microsoft MSRC: Install the security update KB5122871 listed by MSRC
- Microsoft MSRC: Install the security update KB5124008 listed by MSRC
- Microsoft MSRC: Install the security update KB5122880 listed by MSRC
- Microsoft MSRC: Install the security update KB5124012 listed by MSRC
- CISA KEV: 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.
Known exploitation (source facts)
Only what a source states. Unknown means no source has said either way; it is not "not exploited".
- CISA KEV
- Listed
- Exploited (source statement)
- Yes
- Publicly disclosed (source)
- Unknown
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.
Suggested hunting (rule-based inference)
SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.
Matched microsoft-enterprise (Affected product: Windows Server 2025 (Server Core installation), Vendor: Microsoft); local-privilege-escalation (CVSS AV:L, CVSS PR:L)
Exposure
- Identify affected Microsoft products and compare local builds with the MSRC advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · The MSRC product/build mapping establishes applicability. · Rule microsoft-enterprise
- Identify hosts reporting this CVE, prioritising shared or multi-user systems.Telemetry: DeviceTvmSoftwareVulnerabilities · A local, low-privilege vector matters most where untrusted users can run code. · Rule local-privilege-escalation
Exploitation evidence
- Review the advisory's documented behavior on matching hosts before selecting a hunt.Telemetry: DeviceProcessEvents · Product family alone does not justify a CVE-specific detection. · Rule microsoft-enterprise
Show more (2)
Exploitation evidence
- Look for low-privileged processes spawning SYSTEM or root-level child processes on affected hosts.Telemetry: DeviceProcessEvents · Hunting hypothesis from the CVSS vector; privilege transitions are a focused starting point, not evidence of attack. · Rule local-privilege-escalation
Response
- Confirm the source-stated KB or mitigation on matching assets.Telemetry: DeviceTvmSoftwareVulnerabilities · A post-update inventory check verifies remediation. · Rule microsoft-enterprise
CISA KEV Record
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.
Change History & Source Data
— No recorded material change
- CNA / source
- Unknown
- Record status · verification
- UPDATED · Microsoft primary source linked; CISA KEV confirmed
- CPE
- Unknown
Evidence & Provenance
Linked by the query's stored exact CVE association. Review required tables and validation status before use.
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2026-81963"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc