What is CVE-2020-0646?

CVE-2020-0646 is Microsoft .NET Framework Remote Code Execution Vulnerability. The supplied enrichment data classifies it as Injection mapped to CWE-91 CWE-91.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Yes. The supplied enrichment data lists CVE-2020-0646 in CISA KEV with required action: Apply updates per vendor instructions.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

1 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, database audit logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2020-0646 using CVSS 9.8, EPSS 99%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVcriticalInjectionpublic exploit

CVE-2020-0646

CVE-2020-0646 — Microsoft .NET Framework Remote Code Execution Vulnerability

A remote code execution vulnerability exists when the Microsoft .NET Framework fails to validate input properly, aka '.NET Framework Remote Code Execution Injection Vulnerability'.

Published Jan 14, 2020Updated Jun 17, 2026Sources: NVD, CISA, FIRST EPSS

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Nov 3, 2021

EPSS

99%

top of FIRST's scoreset

Affects

microsoft

52 products listed

CVSS base

9.8

critical · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade microsoft_net_framework_4_6_4_6_1_4_6_2_4_7_4_7_1_4_7_2 to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply updates per vendor instructions.

Federal deadline May 3, 2022 — passed 1,597 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
microsoft	microsoft_net_framework_4_6_4_6_1_4_6_2_4_7_4_7_1_4_7_2	—	Vulnerable
microsoft	microsoft_net_framework_4_6_2_4_7_4_7_1_4_7_2	—	Vulnerable
microsoft	microsoft_net_framework_4_8_on_windows_10_version_1803_for_32_bit_systems	—	Vulnerable
microsoft	microsoft_net_framework_4_8_on_windows_10_version_1803_for_x64_based_systems	—	Vulnerable
microsoft	microsoft_net_framework_4_8_on_windows_server_version_1803_server_core_installation	—	Vulnerable
microsoft	microsoft_net_framework_4_8_on_windows_10_version_1709_for_32_bit_systems	—	Vulnerable
microsoft	microsoft_net_framework_4_8_on_windows_10_version_1709_for_x64_based_systems	—	Vulnerable
microsoft	microsoft_net_framework_4_8_on_windows_10_version_1607_for_32_bit_systems	—	Vulnerable
microsoft	microsoft_net_framework_4_8_on_windows_10_version_1607_for_x64_based_systems	—	Vulnerable
microsoft	microsoft_net_framework_4_8_on_windows_server_2016	—	Vulnerable
microsoft	microsoft_net_framework_4_8_on_windows_server_2016_server_core_installation	—	Vulnerable
microsoft	microsoft_net_framework_4_8_on_windows_7_for_32_bit_systems_service_pack_1	—	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.8	CVSS 3.1	critical	3.9	5.9	NVD, CNA
10	CVSS 2.0	high	10	10	NVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Weakness & attack patterns

CWE-91

Inferred from the weakness class — not observed against this CVE.

CAPEC-66 · SQL InjectionCAPEC-7 · Blind SQL Injection

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Nov 3, 2021

Federal deadline

May 3, 2022

passed 1,597 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Exploit entries

Exploit-DB and CTI exploit indexes

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable microsoft_net_framework_4_6_4_6_1_4_6_2_4_7_4_7_1_4_7_2, microsoft_net_framework_4_6_2_4_7_4_7_1_4_7_2, microsoft_net_framework_4_8_on_windows_10_version_1803_for_32_bit_systems, microsoft_net_framework_4_8_on_windows_10_version_1803_for_x64_based_systems, microsoft_net_framework_4_8_on_windows_server_version_1803_server_core_installation, microsoft_net_framework_4_8_on_windows_10_version_1709_for_32_bit_systems, microsoft_net_framework_4_8_on_windows_10_version_1709_for_x64_based_systems, microsoft_net_framework_4_8_on_windows_10_version_1607_for_32_bit_systems, microsoft_net_framework_4_8_on_windows_10_version_1607_for_x64_based_systems, microsoft_net_framework_4_8_on_windows_server_2016, microsoft_net_framework_4_8_on_windows_server_2016_server_core_installation, microsoft_net_framework_4_8_on_windows_7_for_32_bit_systems_service_pack_1, microsoft_net_framework_4_8_on_windows_7_for_x64_based_systems_service_pack_1, microsoft_net_framework_4_8_on_windows_8_1_for_32_bit_systems, microsoft_net_framework_4_8_on_windows_8_1_for_x64_based_systems, microsoft_net_framework_4_8_on_windows_rt_8_1, microsoft_net_framework_4_8_on_windows_server_2008_r2_for_x64_based_systems_service_pack_1, microsoft_net_framework_4_8_on_windows_server_2008_r2_for_x64_based_systems_service_pack_1_server_core_installation, microsoft_net_framework_4_8_on_windows_server_2012, microsoft_net_framework_4_8_on_windows_server_2012_server_core_installation, microsoft_net_framework_4_8_on_windows_server_2012_r2, microsoft_net_framework_4_8_on_windows_server_2012_r2_server_core_installation, microsoft_net_framework_3_5_and_4_8_on_windows_10_version_1809_for_32_bit_systems, microsoft_net_framework_3_5_and_4_8_on_windows_10_version_1809_for_x64_based_systems, microsoft_net_framework_3_5_and_4_8_on_windows_server_2019, microsoft_net_framework_3_5_and_4_8_on_windows_server_2019_server_core_installation, microsoft_net_framework_3_5_and_4_8_on_windows_10_version_1903_for_32_bit_systems, microsoft_net_framework_3_5_and_4_8_on_windows_10_version_1903_for_x64_based_systems, microsoft_net_framework_3_5_and_4_8_on_windows_server_version_1903_server_core_installation, microsoft_net_framework_3_5_and_4_7_2_on_windows_10_version_1809_for_32_bit_systems, microsoft_net_framework_3_5_and_4_7_2_on_windows_10_version_1809_for_x64_based_systems, microsoft_net_framework_3_5_and_4_7_2_on_windows_server_2019, microsoft_net_framework_3_5_and_4_7_2_on_windows_server_2019_server_core_installation, microsoft_net_framework_4_6, microsoft_net_framework_3_0, microsoft_net_framework_3_5, microsoft_net_framework_3_5_1, microsoft_net_framework_4_5_2, microsoft_net_framework_3_5_and_4_8_on_windows_10_version_1909_for_32_bit_systems, microsoft_net_framework_3_5_and_4_8_on_windows_server_version_1909_server_core_installation, microsoft_net_framework_3_5_and_4_8_on_windows_10_version_1909_for_x64_based_systems, microsoft_net_framework_3_5_and_4_7_2_on_windows_server_version_1803_server_core_installation, microsoft_net_framework_3_5_and_4_7_2_on_windows_10_for_32_bit_systems, microsoft_net_framework_3_5_and_4_7_2_on_windows_10_version_1803_for_32_bit_systems, microsoft_net_framework_3_5_and_4_7_2_on_windows_10_version_1803_for_x64_based_systems, microsoft_net_framework_3_5_and_4_7_1_4_7_2_on_windows_10_version_1709_for_x64_based_systems, microsoft_net_framework_3_5_and_4_6_2_4_7_4_7_1_4_7_2_on_windows_server_2016_server_core_installation, microsoft_net_framework_3_5_and_4_7_2_on_windows_10_for_x64_based_systems, 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_systems, microsoft_net_framework_3_5_and_4_7_1_4_7_2_on_windows_10_version_1709_for_32_bit_systems, 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_systems, microsoft_net_framework_3_5_and_4_6_2_4_7_4_7_1_4_7_2_on_windows_server_2016.
Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSdatabase audit logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 9.8 (AV:N)
Jun 17, 2026 · NVD
2021
Added to CISA KEV catalog
Nov 3, 2021 · CISA
2020
Initial · CVE published
Jan 14, 2020 · NVD

References

4 on the record

packetstormsecurity.com/files/156930/SharePoint-Workflows-XOML-Injection.html
Exploit, Third Party Advisory, VDB Entry
portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0646
Patch, Vendor Advisory
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-0646
US Government Resource
nvd.nist.gov/vuln/detail/CVE-2020-0646
Vendor Advisory

Elsewhere on this site

microsoftevery CVE for this vendor
November 2021what else CISA listed
Injectionsame class
CWE-91other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2020-0646 is Microsoft .NET Framework Remote Code Execution Vulnerability, a critical vulnerability affecting microsoft_net_framework_4_6_4_6_1_4_6_2_4_7_4_7_1_4_7_2, microsoft_net_framework_4_6_2_4_7_4_7_1_4_7_2, microsoft_net_framework_4_8_on_windows_10_version_1803_for_32_bit_systems, microsoft_net_framework_4_8_on_windows_10_version_1803_for_x64_based_systems, microsoft_net_framework_4_8_on_windows_server_version_1803_server_core_installation, microsoft_net_framework_4_8_on_windows_10_version_1709_for_32_bit_systems, microsoft_net_framework_4_8_on_windows_10_version_1709_for_x64_based_systems, microsoft_net_framework_4_8_on_windows_10_version_1607_for_32_bit_systems, microsoft_net_framework_4_8_on_windows_10_version_1607_for_x64_based_systems, microsoft_net_framework_4_8_on_windows_server_2016, microsoft_net_framework_4_8_on_windows_server_2016_server_core_installation, microsoft_net_framework_4_8_on_windows_7_for_32_bit_systems_service_pack_1, microsoft_net_framework_4_8_on_windows_7_for_x64_based_systems_service_pack_1, microsoft_net_framework_4_8_on_windows_8_1_for_32_bit_systems, microsoft_net_framework_4_8_on_windows_8_1_for_x64_based_systems, microsoft_net_framework_4_8_on_windows_rt_8_1, microsoft_net_framework_4_8_on_windows_server_2008_r2_for_x64_based_systems_service_pack_1, microsoft_net_framework_4_8_on_windows_server_2008_r2_for_x64_based_systems_service_pack_1_server_core_installation, microsoft_net_framework_4_8_on_windows_server_2012, microsoft_net_framework_4_8_on_windows_server_2012_server_core_installation, microsoft_net_framework_4_8_on_windows_server_2012_r2, microsoft_net_framework_4_8_on_windows_server_2012_r2_server_core_installation, microsoft_net_framework_3_5_and_4_8_on_windows_10_version_1809_for_32_bit_systems, microsoft_net_framework_3_5_and_4_8_on_windows_10_version_1809_for_x64_based_systems, microsoft_net_framework_3_5_and_4_8_on_windows_server_2019, microsoft_net_framework_3_5_and_4_8_on_windows_server_2019_server_core_installation, microsoft_net_framework_3_5_and_4_8_on_windows_10_version_1903_for_32_bit_systems, microsoft_net_framework_3_5_and_4_8_on_windows_10_version_1903_for_x64_based_systems, microsoft_net_framework_3_5_and_4_8_on_windows_server_version_1903_server_core_installation, microsoft_net_framework_3_5_and_4_7_2_on_windows_10_version_1809_for_32_bit_systems, microsoft_net_framework_3_5_and_4_7_2_on_windows_10_version_1809_for_x64_based_systems, microsoft_net_framework_3_5_and_4_7_2_on_windows_server_2019, microsoft_net_framework_3_5_and_4_7_2_on_windows_server_2019_server_core_installation, microsoft_net_framework_4_6, microsoft_net_framework_3_0, microsoft_net_framework_3_5, microsoft_net_framework_3_5_1, microsoft_net_framework_4_5_2, microsoft_net_framework_3_5_and_4_8_on_windows_10_version_1909_for_32_bit_systems, microsoft_net_framework_3_5_and_4_8_on_windows_server_version_1909_server_core_installation, microsoft_net_framework_3_5_and_4_8_on_windows_10_version_1909_for_x64_based_systems, microsoft_net_framework_3_5_and_4_7_2_on_windows_server_version_1803_server_core_installation, microsoft_net_framework_3_5_and_4_7_2_on_windows_10_for_32_bit_systems, microsoft_net_framework_3_5_and_4_7_2_on_windows_10_version_1803_for_32_bit_systems, microsoft_net_framework_3_5_and_4_7_2_on_windows_10_version_1803_for_x64_based_systems, microsoft_net_framework_3_5_and_4_7_1_4_7_2_on_windows_10_version_1709_for_x64_based_systems, microsoft_net_framework_3_5_and_4_6_2_4_7_4_7_1_4_7_2_on_windows_server_2016_server_core_installation, microsoft_net_framework_3_5_and_4_7_2_on_windows_10_for_x64_based_systems, 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_systems, microsoft_net_framework_3_5_and_4_7_1_4_7_2_on_windows_10_version_1709_for_32_bit_systems, 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_systems, microsoft_net_framework_3_5_and_4_6_2_4_7_4_7_1_4_7_2_on_windows_server_2016 from microsoft. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.8 describes technical severity, while EPSS 99% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.