EUVD-2022-3898Published

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 C…

Exploitation and risk

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

CVE-2020-1147

Listed in CISA KEV · added 3 Nov 2021 · Microsoft · .NET Framework, SharePoint, Visual Studio

Microsoft .NET Framework, Microsoft SharePoint, and Visual Studio contain a remote code execution vulnerability when the software fails to check the source markup of XML file input. Successful exploitation allows an attacker to execute code in the context of the process responsible for deserialization of the XML content.

CISA source

FIRST EPSS: 95.80 % · percentile 99.87 % · scored 15 Nov 2026.

Saved 15 Nov 2026 14:45:34 UTC · View this risk record (JSON)

Risk history

Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).

CVE-2020-1147 · 15 Nov 2026 14:45:34 UTC

CVE-2020-1147 · 14 Nov 2026 16:37:01 UTC

CVE-2020-1147 · 13 Nov 2026 19:59:34 UTC

CVE-2020-1147 · 12 Nov 2026 18:18:51 UTC

CVE-2020-1147 · 10 Nov 2026 20:24:10 UTC

CVE-2020-1147 · 09 Nov 2026 21:04:24 UTC

CVE-2020-1147 · 08 Nov 2026 15:12:21 UTC

CVE-2020-1147 · 07 Nov 2026 16:07:52 UTC

CVE-2020-1147 · 06 Nov 2026 19:10:17 UTC

CVE-2020-1147 · 05 Nov 2026 22:49:22 UTC

CVE-2020-1147 · 05 Nov 2026 02:54:06 UTC

CVE-2020-1147 · 03 Nov 2026 16:59:18 UTC

CVE-2020-1147 · 02 Nov 2026 23:59:04 UTC

CVE-2020-1147 · 01 Nov 2026 23:58:58 UTC

CVE-2020-1147 · 01 Nov 2026 03:04:52 UTC

CVE-2020-1147 · 31 Oct 2026 01:52:30 UTC

CVE-2020-1147 · 29 Oct 2026 18:29:26 UTC

CVE-2020-1147 · 28 Oct 2026 19:55:37 UTC

CVE-2020-1147 · 27 Oct 2026 15:46:19 UTC

CVE-2020-1147 · 27 Oct 2026 00:23:05 UTC

CVE-2020-1147 · 25 Oct 2026 15:18:41 UTC

CVE-2020-1147 · 25 Oct 2026 02:24:38 UTC

CVE-2020-1147 · 23 Oct 2026 16:01:26 UTC

Advisory history

14 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

15 Nov 2026 22:18:17 UTC