CVE-2020-1147

CRITICALNVD 7.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 3 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 94%CVSS: 7.8Exploit: cisa kev · ssvc active · Metasploit · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

A remote code execution vulnerability exists in .NET Framework, Microsoft SharePoint, and Visual Studio when the software fails to check the source markup of XML file input, aka '.NET Framework, SharePoint Server, and Visual Studio Remote Code Execution Vulnerability'.

CVSS v3
7.8
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Attend at medium and Act at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
94%
EPSS %ILE
99th
KEV
⚠ Exploited

CISA SSVCTrack at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 14, 2020

Last Modified

October 29, 2025

Advisory Details (5)

Auto-updated Jun 3, 2026
Patch available. Sources: microsoft.
generic
https://www.exploitalert.com/view-details.html?id=35992
microsoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-1147
generic

Packet Storm

http://packetstormsecurity.com/files/163644/Microsoft-SharePoint-Server-2019-Remote-Code-Execution.html
generic

Packet Storm

http://packetstormsecurity.com/files/158876/Microsoft-SharePoint-Server-2019-Remote-Code-Execution.html
generic

Packet Storm

http://packetstormsecurity.com/files/158694/SharePoint-DataSet-DataTable-Deserialization.html

Vendor Advisories for CVE-2020-1147(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatdotnet-0:2.1.516-1.el8_02020-07-17redhat
redhatdotnet-0:2.1.516-1.el8_12020-07-16redhat
redhatrh-dotnet31-dotnet-0:3.1.106-1.el72020-07-15redhat
redhatrh-dotnet21-dotnet-0:2.1.516-1.el72020-07-15redhat
redhatdotnet-0:2.1.516-1.el8_22020-07-15redhat
redhatdotnet3.1-0:3.1.106-1.el8_22020-07-15redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(12 across 1 ecosystem)
NuGet(12)
PackageVulnerable rangeFix by version rangeDependents
Microsoft.NETCore.App2.1.0 ... 2.1.9 (20 versions)
  • 2.1.0 up to 2.1.20: fixed in 2.1.20
—
Microsoft.NETCore.App.Runtime.linux-arm3.1.0 ... 3.1.5 (6 versions)
  • 3.1.0 up to 3.1.6: fixed in 3.1.6
—
Microsoft.NETCore.App.Runtime.linux-arm643.1.0 ... 3.1.5 (6 versions)
  • 3.1.0 up to 3.1.6: fixed in 3.1.6
—
Microsoft.NETCore.App.Runtime.linux-musl-arm643.1.0 ... 3.1.5 (6 versions)
  • 3.1.0 up to 3.1.6: fixed in 3.1.6
—
Microsoft.NETCore.App.Runtime.linux-musl-x643.1.0 ... 3.1.5 (6 versions)
  • 3.1.0 up to 3.1.6: fixed in 3.1.6
—
Microsoft.NETCore.App.Runtime.linux-x643.1.0 ... 3.1.5 (6 versions)
  • 3.1.0 up to 3.1.6: fixed in 3.1.6
—
Microsoft.NETCore.App.Runtime.osx-x643.1.0 ... 3.1.5 (6 versions)
  • 3.1.0 up to 3.1.6: fixed in 3.1.6
—
Microsoft.NETCore.App.Runtime.rhel.6-x643.1.0 ... 3.1.5 (6 versions)
  • 3.1.0 up to 3.1.6: fixed in 3.1.6
—
Microsoft.NETCore.App.Runtime.win-arm3.1.0 ... 3.1.5 (6 versions)
  • 3.1.0 up to 3.1.6: fixed in 3.1.6
—
Microsoft.NETCore.App.Runtime.win-arm643.1.0 ... 3.1.5 (6 versions)
  • 3.1.0 up to 3.1.6: fixed in 3.1.6
—
Microsoft.NETCore.App.Runtime.win-x643.1.0 ... 3.1.5 (6 versions)
  • 3.1.0 up to 3.1.6: fixed in 3.1.6
—
Microsoft.NETCore.App.Runtime.win-x863.1.0 ... 3.1.5 (6 versions)
  • 3.1.0 up to 3.1.6: fixed in 3.1.6
—

Additional Vendor Advisories

(6)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 45× in last 7d / 214× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 932 total refreshes for this CVE.

  1. 2026-10-10 10:02 UTCVendor advisory
  2. 2026-10-10 06:10 UTCVendor advisory
  3. 2026-10-10 02:16 UTCVendor advisory
  4. 2026-10-09 22:23 UTCVendor advisory
  5. 2026-10-09 18:31 UTCVendor advisory
  6. 2026-10-09 14:38 UTCVendor advisory
  7. 2026-10-09 10:44 UTCVendor advisory
  8. 2026-10-09 06:51 UTCVendor advisory
  9. 2026-10-09 02:59 UTCVendor advisory
  10. 2026-10-08 23:07 UTCVendor advisory
  11. 2026-10-08 19:15 UTCVendor advisory
  12. 2026-10-08 15:22 UTCVendor advisory
  13. 2026-10-08 11:30 UTCVendor advisory
  14. 2026-10-08 07:38 UTCVendor advisory
  15. 2026-10-08 03:46 UTCVendor advisory
  16. 2026-10-07 23:53 UTCVendor advisory
  17. 2026-10-07 20:01 UTCVendor advisory
  18. 2026-10-07 16:09 UTCVendor advisory
  19. 2026-10-07 12:17 UTCVendor advisory
  20. 2026-10-07 08:25 UTCVendor advisory
  21. 2026-10-07 04:34 UTCVendor advisory
  22. 2026-10-07 00:42 UTCVendor advisory
  23. 2026-10-06 20:47 UTCVendor advisory
  24. 2026-10-06 16:55 UTCEG score recompute
  25. 2026-10-06 16:55 UTCVendor advisory
Show 75 more
  1. 2026-10-06 15:13 UTCEPSS rescore
  2. 2026-10-06 13:03 UTCVendor advisory
  3. 2026-10-06 09:11 UTCVendor advisory
  4. 2026-10-06 05:19 UTCVendor advisory
  5. 2026-10-06 01:28 UTCVendor advisory
  6. 2026-10-05 21:35 UTCVendor advisory
  7. 2026-10-05 17:42 UTCVendor advisory
  8. 2026-10-05 13:50 UTCVendor advisory
  9. 2026-10-05 09:58 UTCVendor advisory
  10. 2026-10-05 06:07 UTCVendor advisory
  11. 2026-10-05 02:15 UTCVendor advisory
  12. 2026-10-04 22:23 UTCVendor advisory
  13. 2026-10-04 18:31 UTCVendor advisory
  14. 2026-10-04 14:39 UTCVendor advisory
  15. 2026-10-04 10:47 UTCVendor advisory
  16. 2026-10-04 06:53 UTCVendor advisory
  17. 2026-10-04 03:01 UTCVendor advisory
  18. 2026-10-03 23:10 UTCVendor advisory
  19. 2026-10-03 19:14 UTCVendor advisory
  20. 2026-10-03 15:22 UTCVendor advisory
  21. 2026-10-03 11:29 UTCVendor advisory
  22. 2026-10-03 07:37 UTCVendor advisory
  23. 2026-10-03 03:44 UTCVendor advisory
  24. 2026-10-02 23:52 UTCVendor advisory
  25. 2026-10-02 19:59 UTCVendor advisory
  26. 2026-10-02 16:07 UTCVendor advisory
  27. 2026-10-02 12:14 UTCVendor advisory
  28. 2026-10-02 08:20 UTCVendor advisory
  29. 2026-10-02 04:29 UTCVendor advisory
  30. 2026-10-02 00:36 UTCVendor advisory
  31. 2026-10-01 20:44 UTCVendor advisory
  32. 2026-10-01 16:53 UTCVendor advisory
  33. 2026-10-01 12:59 UTCVendor advisory
  34. 2026-10-01 09:07 UTCVendor advisory
  35. 2026-10-01 05:15 UTCVendor advisory
  36. 2026-10-01 01:24 UTCVendor advisory
  37. 2026-09-30 21:32 UTCVendor advisory
  38. 2026-09-30 17:39 UTCEG score recompute
  39. 2026-09-30 17:39 UTCVendor advisory
  40. 2026-09-30 14:59 UTCEPSS rescore
  41. 2026-09-30 13:48 UTCVendor advisory
  42. 2026-09-30 09:54 UTCVendor advisory
  43. 2026-09-30 06:03 UTCVendor advisory
  44. 2026-09-30 02:11 UTCVendor advisory
  45. 2026-09-29 22:20 UTCVendor advisory
  46. 2026-09-29 18:25 UTCVendor advisory
  47. 2026-09-29 14:33 UTCVendor advisory
  48. 2026-09-29 10:42 UTCVendor advisory
  49. 2026-09-29 06:46 UTCVendor advisory
  50. 2026-09-29 02:55 UTCVendor advisory
  51. 2026-09-28 23:03 UTCEG score recompute
  52. 2026-09-28 23:03 UTCVendor advisory
  53. 2026-09-28 19:11 UTCVendor advisory
  54. 2026-09-28 15:15 UTCVendor advisory
  55. 2026-09-28 11:23 UTCVendor advisory
  56. 2026-09-28 07:31 UTCVendor advisory
  57. 2026-09-28 03:40 UTCVendor advisory
  58. 2026-09-27 23:47 UTCVendor advisory
  59. 2026-09-27 21:51 UTCCISA KEV update
  60. 2026-09-27 19:55 UTCVendor advisory
  61. 2026-09-27 16:03 UTCVendor advisory
  62. 2026-09-27 12:12 UTCVendor advisory
  63. 2026-09-27 08:21 UTCVendor advisory
  64. 2026-09-27 04:29 UTCVendor advisory
  65. 2026-09-27 00:35 UTCVendor advisory
  66. 2026-09-26 20:43 UTCVendor advisory
  67. 2026-09-26 16:48 UTCVendor advisory
  68. 2026-09-26 12:56 UTCVendor advisory
  69. 2026-09-26 09:04 UTCVendor advisory
  70. 2026-09-26 05:10 UTCVendor advisory
  71. 2026-09-26 01:16 UTCVendor advisory
  72. 2026-09-25 21:24 UTCVendor advisory
  73. 2026-09-25 19:35 UTCCISA KEV update
  74. 2026-09-25 17:32 UTCVendor advisory
  75. 2026-09-25 14:55 UTCCISA KEV update

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 Metasploit module) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitexploit/windows/http/sharepoint_data_deserialization✓ verified
    First seen Jul 14, 2020

    SharePoint DataSet / DataTable Deserialization

    Open source ↗
  • Exploit-DBEDB-50151
    First seen Jul 23, 2021

    Microsoft SharePoint Server 2019 - Remote Code Execution (2)

    Open source ↗
  • Exploit-DBEDB-48747
    First seen Aug 17, 2020

    Microsoft SharePoint Server 2019 - Remote Code Execution

    Open source ↗

Related CVEs(same product)

Frequently asked(6)

What is CVE-2020-1147?
CVE-2020-1147 is a critical vulnerability published on July 14, 2020. A remote code execution vulnerability exists in .NET Framework, Microsoft SharePoint, and Visual Studio when the software fails to check the source markup of XML file input, aka '.NET Framework, SharePoint Server, and Visual Studio Remote Code Execution Vulnerability'.
When was CVE-2020-1147 disclosed?
CVE-2020-1147 was first published on July 14, 2020, with the most recent update on October 29, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-1147 actively exploited?
Yes. CISA added CVE-2020-1147 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Microsoft .NET Framework, SharePoint, Visual Studio. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2020-1147?
CVE-2020-1147 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2020-1147?
CVE-2020-1147 affects Microsoft .NET Framework, SharePoint, Visual Studio. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2020-1147?
A fix for CVE-2020-1147 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2020-1147 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-1147

Explore →

Is Your Infrastructure Affected by CVE-2020-1147?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs