- Is it exploited?
Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 3 Nov 2021, 659 days after the CVE record was published.
- How likely is exploitation in the next 30 days?
- 99.2%
EPSS score, percentile 99.9 of all scored records
- How severe?
- 9.8 Critical
CVSS v3.1 base score, from CISA's enrichment of the record
- What should I do?
CISA deadline 3 May 2022. Apply updates per vendor instructions.
The CVE record links no vendor advisory, patch or mitigation.
- Which versions are affected?
Affected
- Windows 7 for 32-bit Systems Service Pack 1
- Windows 7 for x64-based Systems Service Pack 1
- Windows 8.1 for 32-bit systems
- Windows 8.1 for x64-based systems
- Windows RT 8.1
- Windows Server 2008 R2 for x64-based Systems Service Pack 1
and 24 more in the table below
Versions by product
Source: CISA Known Exploited Vulnerabilities (KEV) catalog, 2026.10.28, as of 28 Oct 2026; FIRST Exploit Prediction Scoring System (EPSS), v2026.06.15, as of 28 Oct 2026; CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of 28 Oct 2026. About the data.
What to do
Required action, set by CISA
Apply updates per vendor instructions.
CISA due date for this action: 3 May 2022.
Advisories and patches
The CVE record links no vendor advisory, patch or mitigation.
Linked from CISA's catalog entry
Affected products and versions
As listed in the CVE record.
Microsoft Microsoft .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2| Status | Versions |
|---|
| Affected | Windows 7 for 32-bit Systems Service Pack 1 |
| Affected | Windows 7 for x64-based Systems Service Pack 1 |
| Affected | Windows 8.1 for 32-bit systems |
| Affected | Windows 8.1 for x64-based systems |
| Affected | Windows RT 8.1 |
| Affected | Windows Server 2008 R2 for x64-based Systems Service Pack 1 |
| Affected | Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core instal… |
| Affected | Windows Server 2012 |
| Affected | Windows Server 2012 (Server Core installation) |
| Affected | Windows Server 2012 R2 |
| Affected | Windows Server 2012 R2 (Server Core installation) |
Microsoft Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2| Status | Versions |
|---|
| Affected | Windows 10 Version 1607 for 32-bit Systems |
Microsoft Microsoft .NET Framework 4.8 on Windows 10 Version 1803 for 32-bit Systems| Status | Versions |
|---|
| Affected | unspecified |
Microsoft Microsoft .NET Framework 4.8 on Windows 10 Version 1803 for x64-based Systems| Status | Versions |
|---|
| Affected | unspecified |
Microsoft Microsoft .NET Framework 4.8 on Windows Server, version 1803 (Server Core Installation)| Status | Versions |
|---|
| Affected | unspecified |
Microsoft Microsoft .NET Framework 4.8 on Windows 10 Version 1709 for 32-bit Systems| Status | Versions |
|---|
| Affected | unspecified |
Microsoft Microsoft .NET Framework 4.8 on Windows 10 Version 1709 for x64-based Systems| Status | Versions |
|---|
| Affected | unspecified |
Microsoft Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for 32-bit Systems| Status | Versions |
|---|
| Affected | unspecified |
Microsoft Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for x64-based Systems| Status | Versions |
|---|
| Affected | unspecified |
Microsoft Microsoft .NET Framework 4.8 on Windows Server 2016| Status | Versions |
|---|
| Affected | unspecified |
Microsoft Microsoft .NET Framework 4.8 on Windows Server 2016 (Server Core installation)| Status | Versions |
|---|
| Affected | unspecified |
Microsoft Microsoft .NET Framework 4.8 on Windows 7 for 32-bit Systems Service Pack 1| Status | Versions |
|---|
| Affected | unspecified |
Microsoft Microsoft .NET Framework 4.8 on Windows 7 for x64-based Systems Service Pack 1| Status | Versions |
|---|
| Affected | unspecified |
Microsoft Microsoft .NET Framework 4.8 on Windows 8.1 for 32-bit systems| Status | Versions |
|---|
| Affected | unspecified |
Microsoft Microsoft .NET Framework 4.8 on Windows 8.1 for x64-based systems| Status | Versions |
|---|
| Affected | unspecified |
Microsoft Microsoft .NET Framework 4.8 on Windows RT 8.1| Status | Versions |
|---|
| Affected | unspecified |
Microsoft Microsoft .NET Framework 4.8 on Windows Server 2008 R2 for x64-based Systems Service Pack 1| Status | Versions |
|---|
| Affected | unspecified |
Microsoft Microsoft .NET Framework 4.8 on Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)| Status | Versions |
|---|
| Affected | unspecified |
Microsoft Microsoft .NET Framework 4.8 on Windows Server 2012| Status | Versions |
|---|
| Affected | unspecified |
Microsoft Microsoft .NET Framework 4.8 on Windows Server 2012 (Server Core installation)| Status | Versions |
|---|
| Affected | unspecified |
Source: CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of 28 Oct 2026. About the data.
About this vulnerability
Microsoft .NET Framework contains an improper input validation vulnerability that allows for remote code execution.
Summary: CISA's KEV catalog, as of 28 Oct 2026.
- CISA added CVE-2020-0646 to its Known Exploited Vulnerabilities (KEV) catalog on 3 Nov 2021.
- CISA's ransomware flag for this entry is "Unknown": no evidence of ransomware use in the catalog, which is not proof of none.
- The due date CISA sets for the required action is 3 May 2022.
- The CVE record was published on 14 Jan 2020, 659 days before it was added to KEV.
- The CVE record carries a CVSS v3.1 base score of 9.8 (Critical), taken from CISA's enrichment of the record.
- FIRST's EPSS model puts the probability of exploitation in the next 30 days at 99.2% (percentile 99.9), as of 28 Oct 2026.
- CISA's SSVC assessment in the CVE record: exploitation active, automatable yes, technical impact total.
Source: CISA Known Exploited Vulnerabilities (KEV) catalog, 2026.10.28, as of 28 Oct 2026; CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of 28 Oct 2026; FIRST Exploit Prediction Scoring System (EPSS), v2026.06.15, as of 28 Oct 2026. About the data.
Description
A remote code execution vulnerability exists when the Microsoft .NET Framework fails to validate input properly, aka '.NET Framework Remote Code Execution Injection Vulnerability'.
Source: CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of 28 Oct 2026. About the data.
Weakness
- CWE-91: XML Injection (aka Blind XPath Injection)
CWE and CAPEC are maintained by MITRE; the entries are those named in the CVE record and the KEV entry.
Timeline
| Date | Event |
|---|
| 14 Jan 2020 | CVE record published |
| 3 Nov 2021 | Added to CISA KEV |
| 3 May 2022 | CISA due date for the required action |
| 21 Oct 2025 | CVE record last updated |
References
More exploited Microsoft vulnerabilities
- CVE-2026-96951: Microsoft Windows Command Injection Vulnerability (added 13 Oct 2026)
- CVE-2026-65660: Microsoft SharePoint Code Injection Vulnerability (added 25 Sep 2026)
- CVE-2026-81963: Microsoft Windows Link Following Vulnerability (added 8 Sep 2026)
- CVE-2026-85880: Microsoft Windows Heap-Based Buffer Overflow Vulnerability (added 8 Sep 2026)
- CVE-2019-1068: Microsoft SQL Server Remote Code Execution Vulnerability (added 26 Aug 2026)
- CVE-2026-33824: Microsoft Internet Key Exchange (IKE) Service Extensions Double Free Vulnerability (added 18 Aug 2026)