CVE-2020-0646: Microsoft .NET Framework Remote Code Execution
Microsoft .NET Framework · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.
- CVSS v3.1 (CISA ADP)
- 9.8
- critical
- EPSS (exploit probability, 30 days)
- 99.2%
- among the highest 0.1% of all CVEs
- Added to CISA KEV
- 2021-11-03
- US federal due date 2022-05-03
- Automatable (CISA SSVC)
- yes
- technical impact: total
CVE-2020-0646 explained
CVE-2020-0646 is a remote code execution vulnerability in Microsoft .NET Framework on Windows. It occurs because .NET Framework fails to validate input properly, an XML injection weakness. CISA lists it as known to be exploited, so unpatched systems face real risk of takeover.
Impact
An unauthenticated attacker can reach the flaw over the network with low complexity and no user interaction. Successful exploitation can fully compromise confidentiality, integrity and availability. CISA rates it as automatable, so attackers can exploit it at scale, and its technical impact as total, meaning full control of the affected component. CISA lists it in its Known Exploited Vulnerabilities catalog. Known ransomware use is listed as unknown.
Who is affected
The record lists Microsoft .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2 on Windows 7 SP1, Windows 8.1, Windows RT 8.1, Windows Server 2012 and Windows Server 2012 R2, plus 3 more items. It also lists Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 Version 1607 for 32-bit Systems, and .NET Framework 4.8 on several Windows 10 versions, Windows Server 2016 and Windows 7. A further 40 products appear on the page. The CVE record names no fixed version.
Written with AI from the data on this page and checked against it automatically.
Official 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'.
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 .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2AffectedFixed in
- 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 2012
- Windows Server 2012 (Server Core installation)
- Windows Server 2012 R2
- Windows Server 2008 R2 for x64-based Systems Service Pack 1
- Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
- Windows Server 2012 R2 (Server Core installation)
not stated - Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2AffectedFixed in
- Windows 10 Version 1607 for 32-bit Systems
not statedVersion statement as published by the CNA (free text).
- Microsoft .NET Framework 4.8 on Windows 10 Version 1803 for 32-bit SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 4.8 on Windows 10 Version 1803 for x64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 4.8 on Windows Server, version 1803 (Server Core Installation)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 4.8 on Windows 10 Version 1709 for 32-bit SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 4.8 on Windows 10 Version 1709 for x64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for 32-bit SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for x64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 4.8 on Windows Server 2016Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2 |
| not stated |
| Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2Version statement as published by the CNA (free text). |
| not stated |
| Microsoft .NET Framework 4.8 on Windows 10 Version 1803 for 32-bit SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 4.8 on Windows 10 Version 1803 for x64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 4.8 on Windows Server, version 1803 (Server Core Installation)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 4.8 on Windows 10 Version 1709 for 32-bit SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 4.8 on Windows 10 Version 1709 for x64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for 32-bit SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for x64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 4.8 on Windows Server 2016Affected versions are not specified in the CVE record. | – | not stated |
Show 42 more products
- Microsoft .NET Framework 4.8 on Windows Server 2016 (Server Core installation)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 4.8 on Windows 7 for 32-bit Systems Service Pack 1Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 4.8 on Windows 7 for x64-based Systems Service Pack 1Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 4.8 on Windows 8.1 for 32-bit systemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 4.8 on Windows 8.1 for x64-based systemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 4.8 on Windows RT 8.1Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 4.8 on Windows Server 2008 R2 for x64-based Systems Service Pack 1Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 4.8 on Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 4.8 on Windows Server 2012Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 4.8 on Windows Server 2012 (Server Core installation)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 4.8 on Windows Server 2012 R2Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 4.8 on Windows Server 2012 R2 (Server Core installation)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for 32-bit SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for x64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019 (Server Core installation)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1903 for 32-bit SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1903 for x64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.8 on Windows Server, version 1903 (Server Core installation)AffectedFixed in
- 1903
not stated - Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for 32-bit SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for x64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019 (Server Core installation)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 4.6AffectedFixed in
- Windows Server 2008 for 32-bit Systems Service Pack 2
- Windows Server 2008 for x64-based Systems Service Pack 2
not statedVersion statement as published by the CNA (free text).
- Microsoft .NET Framework 3.0AffectedFixed in
- Service Pack 2 on Windows Server 2008 for 32-bit Systems Service Pack 2
- Service Pack 2 on Windows Server 2008 for Itanium-Based Systems Service Pack 2
- Service Pack 2 on Windows Server 2008 for x64-based Systems Service Pack 2
not statedVersion statement as published by the CNA (free text).
- Microsoft .NET Framework 3.5AffectedFixed in
- Windows 8.1 for 32-bit systems
- Windows 8.1 for x64-based systems
- Windows Server 2012
- Windows Server 2012 (Server Core installation)
- Windows Server 2012 R2
- Windows 10 Version 1607 for 32-bit Systems
- Windows Server 2012 R2 (Server Core installation)
not stated - Microsoft .NET Framework 3.5.1AffectedFixed in
- Windows 7 for 32-bit Systems Service Pack 1
- Windows 7 for x64-based Systems Service Pack 1
- Windows Server 2008 R2 for Itanium-Based Systems Service Pack 1
- Windows Server 2008 R2 for x64-based Systems Service Pack 1
- Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
not stated - Microsoft .NET Framework 4.5.2AffectedFixed in
- 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 2012
- Windows Server 2012 (Server Core installation)
- Windows Server 2012 R2
- Windows Server 2008 for 32-bit Systems Service Pack 2
- Windows Server 2008 for x64-based Systems Service Pack 2
- Windows Server 2008 R2 for x64-based Systems Service Pack 1
- Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
- Windows Server 2012 R2 (Server Core installation)
not stated - Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1909 for 32-bit SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.8 on Windows Server, version 1909 (Server Core installation)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1909 for x64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server, version 1803 (Server Core Installation)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 for 32-bit SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1803 for 32-bit SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1803 for x64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.7.1/4.7.2 on Windows 10 Version 1709 for x64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2016 (Server Core installation)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 for x64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 Version 1607 for 32-bit SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.7.1/4.7.2 on Windows 10 Version 1709 for 32-bit SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 Version 1607 for x64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2016Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft .NET Framework 4.8 on Windows Server 2016 (Server Core installation)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 4.8 on Windows 7 for 32-bit Systems Service Pack 1Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 4.8 on Windows 7 for x64-based Systems Service Pack 1Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 4.8 on Windows 8.1 for 32-bit systemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 4.8 on Windows 8.1 for x64-based systemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 4.8 on Windows RT 8.1Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 4.8 on Windows Server 2008 R2 for x64-based Systems Service Pack 1Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 4.8 on Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 4.8 on Windows Server 2012Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 4.8 on Windows Server 2012 (Server Core installation)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 4.8 on Windows Server 2012 R2Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 4.8 on Windows Server 2012 R2 (Server Core installation)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for 32-bit SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for x64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019 (Server Core installation)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1903 for 32-bit SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1903 for x64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows Server, version 1903 (Server Core installation) |
| not stated |
| Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for 32-bit SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for x64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019 (Server Core installation)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 4.6Version statement as published by the CNA (free text). |
| not stated |
| Microsoft .NET Framework 3.0Version statement as published by the CNA (free text). |
| not stated |
| Microsoft .NET Framework 3.5 |
| not stated |
| Microsoft .NET Framework 3.5.1 |
| not stated |
| Microsoft .NET Framework 4.5.2 |
| not stated |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1909 for 32-bit SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows Server, version 1909 (Server Core installation)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1909 for x64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server, version 1803 (Server Core Installation)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 for 32-bit SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1803 for 32-bit SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1803 for x64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.7.1/4.7.2 on Windows 10 Version 1709 for x64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2016 (Server Core installation)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 for x64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 Version 1607 for 32-bit SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.7.1/4.7.2 on Windows 10 Version 1709 for 32-bit SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 Version 1607 for x64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2016Affected 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-05-03 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply the Microsoft security updates for CVE-2020-0646 per the vendor advisory on every affected Windows system.
- Inventory all .NET Framework versions installed across Windows clients and servers, including Server Core installations.
- Prioritize internet-facing and other network-reachable systems, since no authentication or user interaction is required.
- Restrict network exposure of systems running affected .NET Framework versions until updates are confirmed installed.
- Check affected systems for signs of compromise, given that CISA lists the vulnerability as known exploited.
The CVE record names no fixed version, but this does not mean no fix exists. Follow the Microsoft advisory to identify the correct update for each .NET Framework and Windows combination. CISA's required action is to apply updates per vendor instructions. Until updates are applied, limit network exposure of 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
- Yes – attackers can automate it at scale
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-91 XML Injection (aka Blind XPath Injection)
Questions about CVE-2020-0646
- Is CVE-2020-0646 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03, with a US federal due date of 2022-05-03. Whether it has been used in ransomware campaigns is listed as unknown.
- Which update fixes this vulnerability?
- The CVE record does not name fixed versions. CISA's required action is to apply updates per vendor instructions, so use the Microsoft advisory to find the update for each affected .NET Framework and Windows version.
- Does an attacker need credentials or user interaction?
- No. According to the CVSS data, the attack works over the network with low complexity, requires no privileges and no user interaction.
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.