Yes. CISA added CVE-2021-36948 to its Known Exploited Vulnerabilities catalogue on 3 November 2021, which it does only when there is reliable evidence of active exploitation. CISA has not linked it to known ransomware campaigns. Microsoft Windows Update Medic Service contains an unspecified vulnerability that allows for privilege escalation. Any organisation running the affected product should treat remediation as urgent.
What “being exploited in the wild” means for this CVE
For a CVE like this, “in the wild” means more than a theoretical weakness or a lab proof-of-concept. It means defenders should treat the issue as actively exploited until they can prove otherwise. For Windows privilege-escalation bugs, that shifts the priority from normal backlog handling to urgent exposure checks, fast remediation, and validation that the vulnerable service is actually present.
Because the direct answer already confirms CISA KEV listing, the practical question is no longer whether exploitation is credible. The question becomes whether your estate still contains the affected component, whether attackers could have used it before remediation, and whether any local privileges gained through the flaw were leveraged to persist or move laterally. That is the same triage logic covered in the Zero-Day and Exploited Vulnerabilities Guide.
How to confirm exposure and decide what to do next
Start with asset confirmation, not patch wishful thinking. Verify whether Microsoft Windows Update Medic Service is installed and enabled on systems that matter to your environment, then confirm which endpoints are reachable, internet-exposed, or likely to be targeted by a local foothold. If the service is present, assume the risk is operationally real even before you have incident evidence.
When patching is available, remediate on the same urgent path you would use for other KEV-listed issues, then validate that the affected hosts are no longer vulnerable and that the service state matches your baseline. If patching must wait, use compensating controls that reduce the chance of a local attacker getting a privilege jump, and track the exception as a time-bound exposure rather than a standing waiver. For prioritisation and exception handling, the Vulnerability Management Guide is the right operational reference.
Do not stop at patch status alone. For privilege-escalation flaws, the relevant question is whether a lower-privileged process could have used the weakness to reach administrative execution on a host. If you find signs of abuse, treat the endpoint as potentially compromised and move to containment, forensic review, and recovery decisions rather than simple remediation.
What to check for earlier compromise and privilege abuse
Look for suspicious service behavior, unexpected child processes, new scheduled tasks, unusual local administrator changes, and post-exploitation activity on the same hosts that carried the vulnerable service. On Windows systems, attackers often use privilege escalation as a bridge to credential access, persistence, and lateral movement, so the host-level review should not end at the exploited component itself.
If the host held privileged sessions, cached credentials, or admin tooling, widen the search to adjacent systems and accounts. A privilege-escalation flaw can be the first step in a broader intrusion chain, which is why adversary-technique mapping is useful for hunting after the initial alert. The MITRE ATT&CK Enterprise Matrix is the clearest external reference for that kind of post-exploitation analysis.
Where the exploited system is part of a broader access model, inspect whether the attacker could have converted the local escalation into broader control. If administrative access was gained, check for newly created users, altered trust relationships, disabled security tools, or credential material staged for reuse elsewhere. That is the point where exploitation stops being a host issue and becomes an enterprise access issue.
Risk and Threat Considerations
Privilege escalation vulnerabilities matter because they collapse the gap between a low-value foothold and meaningful control of a Windows system. Once an attacker can raise privileges locally, they can disable defenses, harvest credentials, and use the host as a platform for deeper access. CISA KEV inclusion is a strong signal that exploitation is not hypothetical.
Failure mechanism: A local attacker or malware with limited execution rights abuses the vulnerable service to run with elevated privileges, then uses that power to modify the system, hide activity, or pivot to adjacent assets.
Impact: The result can be full host compromise, credential exposure, persistence, and a faster path to lateral movement across the environment, especially if the machine has administrative context or trusted management access.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while CIS Controls v8, NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CIS Controls v8 | CIS-7 — Continuous Vulnerability Management | KEV-listed exploitation makes timely vulnerability prioritisation central to this issue. |
| Recommendation — Prioritise, remediate, and verify exploited vulnerabilities on an urgent SLA. | ||
| NIST SP 800-53 Rev 5 | RA-5 — Vulnerability Monitoring and Scanning | Exposure confirmation and remediation validation are core to this exploited CVE. |
| SI-2 — Flaw Remediation | The CVE requires urgent flaw remediation once active exploitation is confirmed. | |
| Recommendation — Scan for the affected service and validate remediation on all in-scope hosts. Apply the fix or mitigation quickly and track exception handling until resolved. | ||
| MITRE ATT&CK | T1068 — Exploitation for Privilege Escalation | The vulnerability type is privilege escalation, which maps directly to this attack technique. |
| Recommendation — Hunt for privilege-escalation follow-on activity after any suspected exploitation. | ||
| NIST CSF 2.0 | DE.CM-01 — The network is monitored to detect potential cybersecurity events | Earlier compromise checks depend on detecting suspicious host and account behavior. |
| Recommendation — Monitor hosts and accounts for signs that the exploited service was abused. | ||
Practitioner Guidance
What to prioritise: Treat every KEV-listed privilege-escalation issue as an exposure-management problem first and a patching problem second. The first decision is whether the vulnerable service is still present on any business-critical host, especially endpoints with admin tooling or privileged user activity.
What to verify: Confirm that remediation actually removed the exposure, then verify that no evidence of privilege abuse remains on the host. If the system was exposed long enough for exploitation to be plausible, include credential and session review in the same workstream rather than as a follow-up task.
Practitioner takeaway: For exploited Windows privilege-escalation flaws, the useful unit of work is the host plus its access blast radius, not the CVE alone, because local elevation can quickly become enterprise-wide compromise.
Related resources from NHI Mgmt Group
- CVE-2021-36948 (Microsoft Windows Update Medic Service Privilege Escalation)
- Is CVE-2021-34484 (Microsoft Windows User Profile Service Privilege Escalation) being exploited in the wild?
- Is CVE-2021-43226 (Microsoft Windows Privilege Escalation) being exploited in the wild?
- Is CVE-2023-28229 (Microsoft Windows CNG Key Isolation Service Privilege Escalation) being exploited in the wild?