Synced 17 Jun 2026 06:32 UTC Account
← Microsoft Visual Studio

Microsoft Visual Studio vulnerabilities: known CVEs & security history

Microsoft · Developer Tools · 57 tracked CVEs · 0 actively exploited · updated June 2026 · what is a CVE? →

This is the full list of known vulnerabilities (CVEs) across all Microsoft Visual Studio release lines — 57 in total. A CVE here doesn't mean your version is affected — check Microsoft Visual Studio's current status and the safe version to run.

57
known CVEs
0
actively exploited (KEV)
0
critical severity
0
ransomware-linked

Known Microsoft Visual Studio CVEs

Actively-exploited and most-severe first. Open any CVE for full details.

CVESeverityCVSSEPSSYear
CVE-2009-3126 high 9.3 23% 2009
CVE-2009-2528 high 9.3 20% 2009
CVE-2009-2504 high 9.3 21% 2009
CVE-2009-2503 high 9.3 22% 2009
CVE-2009-2501 high 9.3 27% 2009
CVE-2009-2500 high 9.3 23% 2009
CVE-2008-3704 high 9.3 56% 2008
CVE-2025-49739 high 8.8 1% 2025
CVE-2022-35827 high 8.8 2% 2022
CVE-2022-35826 high 8.8 2% 2022
CVE-2022-35825 high 8.8 2% 2022
CVE-2022-35777 high 8.8 2% 2022
CVE-2009-2493 high 8.8 43% 2009
CVE-2009-0901 high 8.8 43% 2009
CVE-2009-2502 high 8.1 22% 2009
CVE-2024-20656 high 7.8 4% 2024
CVE-2023-24897 high 7.8 1% 2023
CVE-2021-28322 high 7.8 1% 2021
CVE-2021-28321 high 7.8 1% 2021
CVE-2021-28313 high 7.8 1% 2021
CVE-2021-3146 high 7.8 0% 2021
CVE-2021-1680 high 7.8 1% 2021
CVE-2021-1651 high 7.8 1% 2021
CVE-2020-16874 high 7.8 4% 2020
CVE-2020-16856 high 7.8 4% 2020
CVE-2020-1393 high 7.8 1% 2020
CVE-2020-1293 high 7.8 1% 2020
CVE-2020-1278 high 7.8 1% 2020
CVE-2020-1257 high 7.8 1% 2020
CVE-2020-1203 high 7.8 1% 2020
CVE-2020-1202 high 7.8 1% 2020
CVE-2019-1232 high 7.8 1% 2019
CVE-2019-0727 high 7.8 1% 2019
CVE-2018-8599 high 7.8 1% 2018
CVE-2018-8172 high 7.8 31% 2018
CVE-2010-3190 high 7.8 9% 2010
CVE-2006-4494 high 7.5 22% 2006
CVE-2001-0153 high 7.5 12% 2001
CVE-2012-0008 medium 6.9 2% 2012
CVE-2014-3802 medium 6.8 11% 2014
CVE-2007-4891 medium 6.8 31% 2007
CVE-2007-4254 medium 6.8 12% 2007
CVE-2007-0468 medium 6.8 25% 2007
CVE-2020-1130 medium 6.6 1% 2020
CVE-2019-1079 medium 6.5 6% 2019
CVE-2009-2495 medium 6.5 42% 2009
CVE-2007-4890 medium 5.8 16% 2007
CVE-2024-43603 medium 5.5 1% 2024
CVE-2023-33139 medium 5.5 1% 2023
CVE-2021-42277 medium 5.5 1% 2021
CVE-2020-1133 medium 5.5 1% 2020
CVE-2019-0537 medium 5.5 8% 2019
CVE-2006-1043 medium 5.1 22% 2006
CVE-2000-0162 medium 5.1 8% 2000
CVE-2018-1037 medium 4.3 6% 2018
CVE-2011-1976 medium 4.3 21% 2011
CVE-2011-1280 medium 4.3 15% 2011

Is my Microsoft Visual Studio version affected?

The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.

Check your Microsoft Visual Studio version → · Monitor Microsoft Visual Studio for new CVEs →

Microsoft Visual Studio vulnerabilities — frequently asked

How many known vulnerabilities does Microsoft Visual Studio have?

IsItPatched tracks 57 CVEs for Microsoft Visual Studio. 0 are critical-severity and 38 high-severity. These span every release line — what matters is whether the version you run is affected.

Does Microsoft Visual Studio have any actively-exploited vulnerabilities?

None of Microsoft Visual Studio's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.

What is the most severe Microsoft Visual Studio vulnerability?

Among tracked issues, CVE-2009-3126 (HIGH, CVSS 9.3) ranks highest — a CWE-189 weakness.

Is Microsoft Visual Studio safe to use?

It depends on the version. The latest supported Microsoft Visual Studio release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.

CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Microsoft Visual Studio security status · Microsoft Visual Studio end-of-life · actively-exploited CVEs. Always verify against Microsoft's advisories — see our disclaimer.