CVE-2020-0638: Microsoft Update Notification Manager Privilege Escalation
Microsoft Update Notification Manager · listed in the CISA catalog of actively exploited vulnerabilities since 2022-05-23.
- CVSS v3.1 (CISA ADP)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 2.5%
- higher than 85.3% of all CVEs
- Added to CISA KEV
- 2022-05-23
- US federal due date 2022-06-13
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2020-0638 explained
CVE-2020-0638 is an elevation of privilege vulnerability in the Microsoft Update Notification Manager on Windows, caused by improper link resolution when the component handles files. CISA lists it as known exploited, including in ransomware campaigns. An attacker who already runs code on a system can use it to gain higher privileges.
Impact
An attacker who already has local code execution with low privileges can elevate privileges without user interaction. A successful attack fully compromises confidentiality, integrity and availability of the affected system. CISA rates the technical impact as total and the vulnerability as not automatable, so each attack needs manual steps. CISA reports active exploitation and known use in ransomware campaigns.
Who is affected
The CVE record lists Microsoft Windows 10 versions 1709, 1803, 1809, 1903 and 1909 for 32-bit, x64 and ARM64-based systems, with one more Windows item shown on the page. It also lists Windows Server 2019 and 2019 (Core installation), plus Server Core installations of versions 1803, 1903 and 1909. The CVE record names no fixed version for any of these products.
Written with AI from the data on this page and checked against it automatically.
Official description
An elevation of privilege vulnerability exists in the way the Update Notification Manager handles files.To exploit this vulnerability, an attacker would first have to gain execution on the victim system, aka 'Update Notification Manager Elevation of Privilege Vulnerability'.
CISA required action: Apply updates per vendor instructions.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft WindowsAffectedFixed in
- 10 Version 1709 for 32-bit Systems
- 10 Version 1803 for 32-bit Systems
- 10 Version 1809 for ARM64-based Systems
- 10 Version 1803 for x64-based Systems
- 10 Version 1709 for ARM64-based Systems
- 10 Version 1709 for x64-based Systems
- 10 Version 1803 for ARM64-based Systems
- 10 Version 1809 for 32-bit Systems
- 10 Version 1809 for x64-based Systems
not statedVersion statement as published by the CNA (free text).
- Microsoft Windows 10 Version 1903 for ARM64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows 10 Version 1903 for 32-bit SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows 10 Version 1903 for x64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows ServerAffectedFixed in
- 2019
- 2019 (Core installation)
- version 1803 (Core Installation)
not stated - Microsoft Windows Server, version 1903 (Server Core installation)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows 10 Version 1909 for 32-bit SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows 10 Version 1909 for x64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows Server, version 1909 (Server Core installation)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows 10 Version 1909 for ARM64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft WindowsVersion statement as published by the CNA (free text). |
| not stated |
| Microsoft Windows 10 Version 1903 for ARM64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows 10 Version 1903 for 32-bit SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows 10 Version 1903 for x64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows Server |
| not stated |
| Microsoft Windows Server, version 1903 (Server Core installation)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows 10 Version 1909 for 32-bit SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows 10 Version 1909 for x64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows Server, version 1909 (Server Core installation)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows 10 Version 1909 for ARM64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: portal.msrc.microsoft.com/en-US/security-guidance/advisor…
- CISA's deadline for US federal agencies: 2022-06-13 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply the Microsoft security update for CVE-2020-0638 on all affected Windows 10 and Windows Server systems, as described in the vendor advisory.
- Prioritize patching, since CISA lists the flaw as known exploited and used in ransomware.
- Limit who can log on or run code on affected systems, and enforce least privilege for user accounts.
- Check affected systems for signs of compromise, such as unexpected privilege changes or unknown administrative accounts.
- Replace or upgrade Windows versions that no longer receive Microsoft security updates.
The CVE record names no fixed version. Follow the Microsoft advisory to identify the correct security update for each affected Windows version. CISA's required action is to apply updates per vendor instructions. Until updates are installed, restrict local access and code execution on affected systems and monitor for signs of compromise.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-59 Improper Link Resolution Before File Access ('Link Following')
Questions about CVE-2020-0638
- Can this vulnerability be exploited remotely?
- Not directly. The attack vector is local, and an attacker must first gain code execution on the target system. The flaw is then used to escalate privileges.
- Is CVE-2020-0638 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-05-23 and notes known ransomware use. US federal agencies had to remediate by 2022-06-13.
- Which update fixes it?
- The CVE record names no fixed version. Use the Microsoft advisory to find the security update for your Windows version and apply it, as CISA requires.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.