Windows Update Medic Service Elevation of Privilege Vulnerability (CVE-2021-36948) Analysis and Mitigation Guide
Executive & SecOps Summary
SECOPS ASSESSMENTAll supported versions of Windows 10, Windows 11, and Windows Server
A local attacker with low privileges can execute arbitrary code with SYSTEM privileges, leading to complete system compromise
Apply the latest Microsoft Cumulative Updates immediately, or temporarily disable the affected service in air-gapped environments
Affected Products & Version Scope
Remediation & Live Workaround Commands
PATCH & WORKAROUND1. Official Patch & Version Upgrade Commands
The primary remediation is to apply the official security updates provided by Microsoft. Use the following PowerShell commands to force-install the latest cumulative updates.
# Install Windows Update module and apply all pending security patches
Install-Module PSWindowsUpdate -Force -SkipPublisherCheck
Get-WindowsUpdate -AcceptAll -Install -AutoReboot2. Temporary Workaround & Hardening Configuration
If patching cannot be performed immediately, you can temporarily disable the Windows Update Medic Service to mitigate the risk. Note that this may affect Windows Update repair capabilities.
# Stop and disable the Windows Update Medic Service
Stop-Service -Name 'WaaSMedicSvc' -Force
Set-Service -Name 'WaaSMedicSvc' -StartupType Disabled
# Force disable via Registry to prevent unauthorized reactivation
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Services\WaaSMedicSvc' -Name 'Start' -Value 43. Log Audit & IoC Verification Commands
Run the following PowerShell script to inspect the System event logs for any unauthorized changes or state transitions related to the Windows Update Medic Service.
# Query System Event Logs for WaaSMedicSvc startup type changes
Get-WinEvent -FilterHashtable @{
LogName='System'
ProviderName='Service Control Manager'
Id=7040
} | Where-Object { $_.Message -like '*Windows Update Medic Service*' } | Format-Table TimeCreated, Message -Width 100Block Kernel Privilege Escalation & Ransomware Payloads Before You Can Reboot
Protect unpatched Windows, Linux, and macOS workloads against in-memory exploitation and lateral movement with autonomous EDR.
Technical Root Cause & Exploitation Mechanics
1. Vulnerability Overview & Root Cause
This vulnerability (CVE-2021-36948) is a local privilege escalation (LPE) vulnerability in the Windows Update Medic Service (WaaSMedicSvc). WaaSMedicSvc is designed to repair and protect Windows Update components and runs under the highly privileged 'NT AUTHORITY\SYSTEM' account. The root cause lies in the improper validation of resources, file paths, or registry keys handled by the service, allowing a local attacker to manipulate these inputs to hijack the service execution flow.
2. Exploitation Mechanics & Attack Scenario
To exploit this vulnerability, an attacker must first gain local access to the target system with standard user privileges. The attacker then manipulates specific symbolic links, registry entries, or DLL paths that WaaSMedicSvc accesses during its routine operations. When the service is triggered, it processes the manipulated resources under the SYSTEM context, resulting in the execution of the attacker's malicious payload with elevated privileges. This vulnerability has been actively exploited in the wild and is listed in the CISA KEV catalog.
3. Infrastructure & Business Impact
Successful exploitation allows an attacker to bypass local security boundaries and gain full administrative control over the endpoint or server. In an enterprise environment, this can be leveraged as a stepping stone for lateral movement, credential dumping (e.g., LSASS), ransomware deployment, and establishing persistent access within the Active Directory domain.
Official Vendor Advisories & References
Windows Update Medic Service Elevation of Privilege Vulnerability
Frequently Asked SecOps Questions (CVE-2021-36948)
FAQQ1. How critical is CVE-2021-36948 and is it actively exploited in the wild?
CVE-2021-36948 is rated CVSS 7.8 (HIGH) with a 30-day EPSS exploitation probability of 23.3%. It is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, requiring immediate emergency remediation.
Q2. Which vendors and products are affected by CVE-2021-36948?
Primary impacted vendors include microsoft across windows, windows_server. Scope summary: All Windows 10, Windows 11, and Windows Server editions where Windows Update Medic Service is active
Q3. What temporary mitigations or workarounds exist for CVE-2021-36948 before patching?
[Mitigation] Apply the latest Microsoft Cumulative Updates immediately, or temporarily disable the affected service in air-gapped environments Follow the CLI remediation commands and interactive SecOps checklist on this page to restrict exposure prior to your maintenance window.
Generate an Internal Engineering Notice or CISO Report for CVE-2021-36948
Instantly format this advisory into an executive CISO summary or engineering patch ticket.
🔗 Related Advisories in Similar Stack (microsoft)
View Category →Windows IKE Extension Double Free Remote Code Execution Vulnerability (CVE-2026-33824)
[Affected Scope] Internet Key Exchange (IKE) Extension service running on Microsoft Windows and Windows Server operating systems
Windows Remote Access Connection Manager (RasMan) Null Pointer Dereference Local DoS Vulnerability (CVE-2026-21525) Technical Advisory
[Affected Scope] Windows and Windows Server operating systems utilizing the Windows Remote Access Connection Manager (RasMan) service.
Windows ALPC Heap-Based Buffer Overflow Privilege Escalation Vulnerability (CVE-2026-85880) Security Advisory
[Affected Scope] Locally authenticated users across Microsoft Windows operating systems
Windows Update Stack Privilege Escalation Vulnerability via Link Following (CVE-2026-81963) Technical Advisory
[Affected Scope] Microsoft Windows operating systems utilizing the Windows Update Stack
Subscribe to Daily Vulnerability Briefings & KEV Alerts
Concise morning briefings for SecOps, DevSecOps, and SRE teams covering newly exploited CVEs and mitigation priorities.