Patch & vulnerability status
Visual Studio 2017 15.9.81
Latest tracked version 15.9.81. Release status, tracked CVEs, and automated cross-platform patching for Visual Studio 2017.
| Platform | Latest version | CVEs tracked | Last checked |
|---|---|---|---|
| Windows | 15.9.81 | 18 | 2026-08-10 |
Known vulnerabilities (CVEs) in Visual Studio 2017
Lavawall tracks 18 published CVEs affecting Visual Studio 2017, and deploys the versions that fix them automatically across your fleet.
| CVE | Published | Severity | Details | Vector |
|---|---|---|---|---|
| CVE-2022-24767 | 2022-04-12 18:15:10 | HIGH (8) | GitHub: Git for Windows' uninstaller vulnerable to DLL hijacking when run under the SYSTEM user account. | LOCAL |
| CVE-2022-21871 | 2022-01-11 21:15:11 | HIGH (8) | Microsoft Diagnostics Hub Standard Collector Runtime Elevation of Privilege Vulnerability | LOCAL |
| CVE-2020-1393 | 2020-07-14 23:15:16 | HIGH (8) | An elevation of privilege vulnerability exists when the Windows Diagnostics Hub Standard Collector Service fails to properly sanitize input, leading to an unsecure library-loading behavior, aka 'Windows Diagnostics Hub Elevation of Privilege Vulnerability'. This CVE ID is unique from CVE-2020-1418. | LOCAL |
| CVE-2020-1147 | 2020-07-14 23:15:12 | HIGH (8) | A remote code execution vulnerability exists in .NET Framework, Microsoft SharePoint, and Visual Studio when the software fails to check the source markup of XML file input, aka '.NET Framework, SharePoint Server, and Visual Studio Remote Code Execution Vulnerability'. | LOCAL |
| CVE-2020-0899 | 2020-04-15 15:15:14 | MEDIUM (6) | An elevation of privilege vulnerability exists when Microsoft Visual Studio updater service improperly handles file permissions, aka 'Microsoft Visual Studio Elevation of Privilege Vulnerability'. | LOCAL |
| CVE-2020-0884 | 2020-03-12 16:15:20 | LOW (4) | A spoofing vulnerability exists in Microsoft Visual Studio as it includes a reply URL that is not secured by SSL, aka 'Microsoft Visual Studio Spoofing Vulnerability'. | NETWORK |
| CVE-2019-1354 | 2020-01-24 21:15:13 | HIGH (9) | A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1349, CVE-2019-1350, CVE-2019-1352, CVE-2019-1387. | NETWORK |
| CVE-2019-1352 | 2020-01-24 21:15:13 | HIGH (9) | A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1349, CVE-2019-1350, CVE-2019-1354, CVE-2019-1387. | NETWORK |
| CVE-2019-1351 | 2020-01-24 21:15:13 | HIGH (8) | A tampering vulnerability exists when Git for Visual Studio improperly handles virtual drive paths, aka 'Git for Visual Studio Tampering Vulnerability'. | NETWORK |
| CVE-2019-1350 | 2020-01-24 21:15:13 | HIGH (9) | A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1349, CVE-2019-1352, CVE-2019-1354, CVE-2019-1387. | NETWORK |
| CVE-2019-1349 | 2020-01-24 21:15:13 | HIGH (9) | A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1350, CVE-2019-1352, CVE-2019-1354, CVE-2019-1387. | NETWORK |
| CVE-2019-1211 | 2019-08-14 21:15:18 | LOW (4) | An elevation of privilege vulnerability exists in Git for Visual Studio when it improperly parses configuration files. An attacker who successfully exploited the vulnerability could execute code in the context of another local user. To exploit the vulnerability, an authenticated attacker would need to modify Git configuration files on a system prior to a full installation of the application. The attacker would then need to convince another user on the system to execute specific Git commands. The update addresses the issue by changing the permissions required to edit configuration files. | LOCAL |
| CVE-2019-0546 | 2019-01-08 21:29:01 | HIGH (9) | A remote code execution vulnerability exists in Visual Studio when the C++ compiler improperly handles specific combinations of C++ constructs, aka "Visual Studio Remote Code Execution Vulnerability." This affects Microsoft Visual Studio. | NETWORK |
| CVE-2018-8599 | 2018-12-12 00:29:01 | MEDIUM (5) | An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector Service improperly impersonates certain file operations, aka "Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability." This affects Microsoft Visual Studio, Windows Server 2019, Windows Server 2016, Windows 10, Windows 10 Servers. | LOCAL |
| CVE-2018-8232 | 2018-07-11 00:29:01 | MEDIUM (5) | A Tampering vulnerability exists when Microsoft Macro Assembler improperly validates code, aka "Microsoft Macro Assembler Tampering Vulnerability." This affects Microsoft Visual Studio. | LOCAL |
| CVE-2018-8172 | 2018-07-11 00:29:00 | HIGH (8) | 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." This affects Microsoft Visual Studio, Expression Blend 4. | LOCAL |
| CVE-2018-1037 | 2018-04-12 01:29:10 | MEDIUM (4) | An information disclosure vulnerability exists when Visual Studio improperly discloses limited contents of uninitialized memory while compiling program database (PDB) files, aka "Microsoft Visual Studio Information Disclosure Vulnerability." This affects Microsoft Visual Studio. | NETWORK |
| CVE-2018-0952 | 2018-08-15 17:29:00 | HIGH (7) | 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, Windows 10 Servers. | LOCAL |
Why keeping Visual Studio 2017 patched matters
Unpatched third-party applications are one of the most common ways attackers get in: 57% of breached MSP clients and 32% of ransomware cases trace back to a missing patch. Every Visual Studio 2017 release that fixes a security bug is public, so attackers see it too, and an out-of-date install becomes a documented way in. Tracking the installed version on every machine and closing the gap quickly is what turns a disclosed CVE into a non-event.
How Lavawall® patches Visual Studio 2017
Lavawall® watches Visual Studio 2017 releases and CVEs continuously, ranks each update by risk, and deploys it across your whole fleet, Windows, macOS, and Linux, from a single agent, independently of your RMM. You get one place to see which machines are behind on Visual Studio 2017, one policy to bring them current, and timestamped evidence for audits.
Frequently asked questions
What is the latest version of Visual Studio 2017?
Lavawall tracks Visual Studio 2017 at version 15.9.81 (last checked 2026-08-10). New releases are monitored continuously and can be deployed automatically across your fleet.
Lavawall tracks Visual Studio 2017 at version 15.9.81 (last checked 2026-08-10). New releases are monitored continuously and can be deployed automatically across your fleet.
Does Visual Studio 2017 have known security vulnerabilities (CVEs)?
Lavawall tracks 18 CVEs for Visual Studio 2017 and remediates them automatically as part of patching.
Lavawall tracks 18 CVEs for Visual Studio 2017 and remediates them automatically as part of patching.
How do I patch Visual Studio 2017 automatically?
Deploy the Lavawall® agent and Visual Studio 2017 updates are applied automatically across Windows, macOS, and Linux, risk-ranked and reported, independently of your RMM.
Deploy the Lavawall® agent and Visual Studio 2017 updates are applied automatically across Windows, macOS, and Linux, risk-ranked and reported, independently of your RMM.
Lavawall® monitors releases and CVEs for Visual Studio 2017 through public information and proprietary statistical analysis, and can patch it automatically across your fleet.