Sign inStart freeBook a demo

Visual Studio vulnerabilitiesRanked by how likely they are to be used.

Product12 versions
The short answer

Visual Studio is made by Microsoft. We track 56 published vulnerabilities listed under that exact name, across 12 versions. None of them is on the list of flaws known to be exploited today. Microsoft lists newer releases under their own names, such as Visual Studio 2019, so check those pages too.

See the riskiest flaws

We keep watching the known-exploited list.

Other names

Is Visual Studio listed under other names? Yes.

Microsoft also lists Visual Studio under more specific names, such as Visual Studio 2019 and Visual Studio 2022. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.

Known exploited

Which Visual Studio vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Visual Studio's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Visual Studio 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.

50% or more10% to 49%Under 10%
  1. 34%
    CVE-2009-2495Medium

    The Active Template Library (ATL) in Microsoft Visual Studio .NET 2003 SP1, Visual Studio 2005 SP1 and 2008 Gold and SP1, and Visual C++ 2005 SP1 and 2008 Gold and SP1 does not properly enforce string termination,...

    CVSS6.5Published29 Jul 2009
  2. 34%
    CVE-2018-8172High

    A remote code execution vulnerability exists in Visual Studio software when the software does not check the source markup of a file for an unbuilt project, aka "Visual Studio Remote Code Execution Vulnerability."...

    CVSS7.8Published11 Jul 2018
  3. 25%
    CVE-2007-0468Medium

    Stack-based buffer overflow in rcdll.dll in msdev.exe in Visual C++ (MSVC) in Microsoft Visual Studio 6.0 SP6 allows user-assisted remote attackers to execute arbitrary code via a long file path in the "1 TYPELIB...

    CVSS6.8Published24 Jan 2007
Precursor Intelligence

Running Visual Studio? 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.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Start free →Book a demo

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 56 published vulnerabilities listed under the name Visual Studio, across 12 versions.

None of Visual Studio's vulnerabilities is on the list of flaws known to be exploited today.

Microsoft also lists Visual Studio under more specific names, such as Visual Studio 2019 and Visual Studio 2022. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

Create a Precursor Intelligence account and track Visual Studio. 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.

Keep exploring