# Visual Studio 2017 vulnerabilities > Visual Studio 2017 is made by Microsoft. We track 90 published vulnerabilities in it, across 128 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 2017, check your version against the exploited flaws below and patch those first. Canonical page: https://www.precursorintelligence.com/product/microsoft/visual_studio_2017 ## At a glance - **Made by:** [Microsoft](https://www.precursorintelligence.com/vendors/microsoft) - **Published vulnerabilities:** 90 - **Known to be exploited:** 1 - **Versions tracked:** 128 - **Most recently added to the known-exploited list:** [CVE-2020-1147](https://www.precursorintelligence.com/what-is/cve-2020-1147), 3 November 2021. We keep watching the list. ## Which versions of Visual Studio 2017 do the exploited flaws hit? Each exploited flaw lists the versions it affects, as published. - [CVE-2020-1147](https://www.precursorintelligence.com/what-is/cve-2020-1147) (Microsoft .NET Framework, SharePoint, and Visual Studio Remote Code Execution Vulnerability): 15.0 to 15.9 ## Which Visual Studio 2017 vulnerabilities are being exploited? 1 flaw is on the government list of vulnerabilities known to be exploited, newest first: - [CVE-2020-1147](https://www.precursorintelligence.com/what-is/cve-2020-1147): Microsoft .NET Framework, SharePoint, and Visual Studio Remote Code Execution Vulnerability. High, CVSS 7.8, chance of use in 30 days 94%, known exploited since 3 November 2021. ## Which Visual Studio 2017 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): - [CVE-2020-1147](https://www.precursorintelligence.com/what-is/cve-2020-1147): 94%, High (CVSS 7.8), known exploited - [CVE-2021-36952](https://www.precursorintelligence.com/what-is/cve-2021-36952): 51%, High (CVSS 7.8) - [CVE-2018-8172](https://www.precursorintelligence.com/what-is/cve-2018-8172): 34%, High (CVSS 7.8) - [CVE-2019-0546](https://www.precursorintelligence.com/what-is/cve-2019-0546): 16%, High (CVSS 7.8) - [CVE-2019-0613](https://www.precursorintelligence.com/what-is/cve-2019-0613): 15%, High (CVSS 8.8) - [CVE-2019-0809](https://www.precursorintelligence.com/what-is/cve-2019-0809): 11%, High (CVSS 7.8) ## Questions ### How many vulnerabilities does Visual Studio 2017 have? We track 90 published vulnerabilities listed under the name Visual Studio 2017, across 128 versions. The most recent Visual Studio 2017 flaw added to the known-exploited list is CVE-2020-1147, on 3 November 2021. ### Which Visual Studio 2017 vulnerabilities are being exploited? 1 is on the list of flaws known to be exploited. The most recently added is CVE-2020-1147. ### Which versions of Visual Studio 2017 do the exploited flaws affect? Each flaw names its own versions, usually as ranges. The newest, CVE-2020-1147, affects 15.0 to 15.9. The versions for every exploited flaw are listed on this page. ### How do I get alerts for Visual Studio 2017? Create a Precursor Intelligence account and track Visual Studio 2017. 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. ## Running Visual Studio 2017? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact