Answer in brief
CVE-2020-0638 records a High severity vulnerability in CVE Program Container. The current sources mark it as known exploited. The current feed maps Microsoft/Windows (generic), Microsoft/Windows 10 Version 1903 for 32-bit Systems (generic), Microsoft/Windows 10 Version 1903 for ARM64-based Systems (generic), Microsoft/Windows 10 Version 1903 for x64-based Systems (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. Known-exploitation status makes exposure review time-sensitive. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Microsoft/Windows (generic), Microsoft/Windows 10 Version 1903 for 32-bit Systems (generic), Microsoft/Windows 10 Version 1903 for ARM64-based Systems (generic), Microsoft/Windows 10 Version 1903 for x64-based Systems (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Microsoft/Windowsgeneric | 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 reported |
| Microsoft/Windows 10 Version 1903 for 32-bit Systemsgeneric | unspecified | Not reported |
| Microsoft/Windows 10 Version 1903 for ARM64-based Systemsgeneric | unspecified | Not reported |
| Microsoft/Windows 10 Version 1903 for x64-based Systemsgeneric | unspecified | Not reported |
| Microsoft/Windows 10 Version 1909 for 32-bit Systemsgeneric | unspecified | Not reported |
| Microsoft/Windows 10 Version 1909 for ARM64-based Systemsgeneric | unspecified | Not reported |
| Microsoft/Windows 10 Version 1909 for x64-based Systemsgeneric | unspecified | Not reported |
| Microsoft/Windows Servergeneric | 2019 || 2019 (Core installation) || version 1803 (Core Installation) | Not reported |
| Microsoft/Windows Server, version 1903 (Server Core installation)generic | unspecified | Not reported |
| Microsoft/Windows Server, version 1909 (Server Core installation)generic | unspecified | Not reported |
Published upstream
Jan 14, 2020
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2025
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
May 24, 2026
Added to CISA KEV
May 23, 2022
Evidence: source:kev:kev:kev:recordAn 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'.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2020-0638 records a High severity vulnerability in CVE Program Container. The current sources mark it as known exploited. The current feed maps Microsoft/Windows (generic), Microsoft/Windows 10 Version 1903 for 32-bit Systems (generic), Microsoft/Windows 10 Version 1903 for ARM64-based Systems (generic), Microsoft/Windows 10 Version 1903 for x64-based Systems (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. Known-exploitation status makes exposure review time-sensitive. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Microsoft/Windows (generic), Microsoft/Windows 10 Version 1903 for 32-bit Systems (generic), Microsoft/Windows 10 Version 1903 for ARM64-based Systems (generic), Microsoft/Windows 10 Version 1903 for x64-based Systems (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Microsoft/Windowsgeneric | 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 reported |
| Microsoft/Windows 10 Version 1903 for 32-bit Systemsgeneric | unspecified | Not reported |
| Microsoft/Windows 10 Version 1903 for ARM64-based Systemsgeneric | unspecified | Not reported |
| Microsoft/Windows 10 Version 1903 for x64-based Systemsgeneric | unspecified | Not reported |
| Microsoft/Windows 10 Version 1909 for 32-bit Systemsgeneric | unspecified | Not reported |
| Microsoft/Windows 10 Version 1909 for ARM64-based Systemsgeneric | unspecified | Not reported |
| Microsoft/Windows 10 Version 1909 for x64-based Systemsgeneric | unspecified | Not reported |
| Microsoft/Windows Servergeneric | 2019 || 2019 (Core installation) || version 1803 (Core Installation) | Not reported |
| Microsoft/Windows Server, version 1903 (Server Core installation)generic | unspecified | Not reported |
| Microsoft/Windows Server, version 1909 (Server Core installation)generic | unspecified | Not reported |
Published upstream
Jan 14, 2020
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2025
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
May 24, 2026
Added to CISA KEV
May 23, 2022
Evidence: source:kev:kev:kev:recordAn 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'.
Quoted source text, attributed separately from HOL analysis.