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

Product1 versions
The short answer

Visual Studio 2015 is made by Microsoft. We track 4 published vulnerabilities in it, across 1 version. None of them is on the list of flaws known to be exploited today. If you run Visual Studio 2015, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Visual Studio 2015 vulnerabilities are being exploited?

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

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

Exploit likelihood

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

    An Elevation of Privilege vulnerability exists when Diagnostics Hub Standard Collector allows file creation in arbitrary locations, aka "Diagnostic Hub Standard Collector Elevation Of Privilege Vulnerability." This...

    CVSS7.8Published15 Aug 2018
  2. 1.0%

    An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector or the Visual Studio Standard Collector allows file creation in arbitrary locations.To exploit the vulnerability, an attacker...

    CVSS7.8Published12 Mar 2020
  3. 0.8%

    An elevation of privilege vulnerability exists when the Visual Studio Extension Installer Service improperly handles file operations, aka 'Visual Studio Extension Installer Service Elevation of Privilege Vulnerability'.

    CVSS5.5Published15 Apr 2020
  4. 0.8%

    An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector Service improperly handles file operations, aka 'Diagnostics Hub Standard Collector Elevation of Privilege Vulnerability'.

    CVSS7.8Published12 Mar 2020
Precursor Intelligence

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

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 4 published vulnerabilities listed under the name Visual Studio 2015, across 1 version.

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

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