Visual Studio 2019 vulnerabilitiesAnd the versions its exploited flaws hit.
Visual Studio 2019 is made by Microsoft. We track 115 published vulnerabilities in it, across 305 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 3 November 2021. If you run Visual Studio 2019, check your version against the exploited flaws below and patch those first.
The most recent Visual Studio 2019 flaw added to the known-exploited list is CVE-2020-1147, on 3 November 2021. We keep watching the known-exploited list.
Which versions of Visual Studio 2019 do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2020-1147Exploited list, 3 Nov 2021
Microsoft .NET Framework, SharePoint, and Visual Studio Remote Code Execution Vulnerability
16.0 to 16.6
Which Visual Studio 2019 vulnerabilities are being exploited?
1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 7.8Microsoft .NET Framework, SharePoint, and Visual Studio Remote Code Execution Vulnerability
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.
Which Visual Studio 2019 flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 94%
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,...
- 54%CVE-2021-27068High
Visual Studio Remote Code Execution Vulnerability
- 51%CVE-2021-36952High
Visual Studio Remote Code Execution Vulnerability
- 30%CVE-2021-26701High
.NET Core Remote Code Execution Vulnerability
- 20%CVE-2021-41355Medium
.NET Core and Visual Studio Information Disclosure Vulnerability
- 8.7%CVE-2019-1351High
A tampering vulnerability exists when Git for Visual Studio improperly handles virtual drive paths, aka 'Git for Visual Studio Tampering Vulnerability'.
Running Visual Studio 2019? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
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.
- Matched to
- Visual Studio 2019 on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 115 published vulnerabilities listed under the name Visual Studio 2019, across 305 versions. The most recent Visual Studio 2019 flaw added to the known-exploited list is CVE-2020-1147, on 3 November 2021.
1 is on the list of flaws known to be exploited. The most recently added is CVE-2020-1147.
Each flaw names its own versions, usually as ranges. The newest, CVE-2020-1147, affects 16.0 to 16.6. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Visual Studio 2019. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.