Microsoft Visual Studio 2013
13 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Microsoft Visual Studio 2013, a product in the devtools ci space. Use it to gauge the current risk picture and drill into individual advisories.
Microsoft Visual Studio 2013 CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 13 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- High10
- Medium3
Latest CVEs
The 13 most recently published vulnerabilities affecting Microsoft Visual Studio 2013.
- CVE-2023-24897.NET, .NET Framework, and Visual Studio Remote Code Execution Vulnerability7.8
- CVE-2023-33139Visual Studio Information Disclosure Vulnerability5.5
- CVE-2023-27910A user may be tricked into opening a malicious FBX file that may exploit a stack buffer overflow vulnerability in Autodesk® FBX® SDK 2020 or prior which may lead to code execution.7.8
- CVE-2023-27909An Out-Of-Bounds Write Vulnerability in Autodesk® FBX® SDK version 2020 or prior may lead to code execution through maliciously crafted FBX files or information disclosure.7.8
- CVE-2023-27911A user may be tricked into opening a malicious FBX file that may exploit a heap buffer overflow vulnerability in Autodesk® FBX® SDK 2020 or prior which may lead to code execution.7.8
- CVE-2022-35826Visual Studio Remote Code Execution Vulnerability8.8
- CVE-2022-35825Visual Studio Remote Code Execution Vulnerability8.8
- CVE-2022-35777Visual Studio Remote Code Execution Vulnerability8.8
- CVE-2020-16874Visual Studio Remote Code Execution Vulnerability7.8
- CVE-2020-16856Visual Studio Remote Code Execution Vulnerability7.8
- CVE-2019-1079An information disclosure vulnerability exists when Visual Studio improperly parses XML input in certain settings files, aka 'Visual Studio Information Disclosure Vulnerability'.6.5
- CVE-2018-8172A 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 ...7.8
- CVE-2018-1037An information disclosure vulnerability exists when Visual Studio improperly discloses limited contents of uninitialized memory while compiling program database (PDB) files, aka "Microsoft Visual S...4.3
Product grouping is registry-driven, with AI assist and human review. How it works