Improper link resolution before file access ('link following') in Visual Studio allows an unauthorized attacker to elevate privileges over a network.
Product
Microsoft visual studio 2015 vulnerabilities
8 published CVES affecting Microsoft visual studio 2015, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 8
- Critical
- 0
- High
- 7
- Medium
- 1
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest Microsoft visual studio 2015 CVEs
Newest publication first
-
HighCVSS 8.8 EPSS 0.95%
-
HighCVSS 7.5 EPSS 1.8%
.NET and Visual Studio Remote Code Execution Vulnerability
-
HighCVSS 8.8 EPSS 1.6%
Visual Studio Remote Code Execution Vulnerability
-
CVE-2025-21176 .NET, .NET Framework, and Visual Studio Remote Code Execution Vulnerability
PublishedHighCVSS 8.8 EPSS 2.4%.NET, .NET Framework, and Visual Studio Remote Code Execution Vulnerability
-
MediumCVSS 5.5 EPSS 0.81%
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'.
-
HighCVSS 7.8 EPSS 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 would first have to log on to the system.An attacker could then...
-
HighCVSS 7.8 EPSS 0.79%
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'.
-
HighCVSS 7.8 EPSS 6.2% Public exploit
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 affects Windows Server 2016, Windows 10, Microsoft Visual Studio,...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.