Patch & vulnerability status
Microsoft Corporation
Microsoft Visual Studio Code 1.111
Latest tracked version 1.111. Release status, tracked CVEs, and automated cross-platform patching for Microsoft Visual Studio Code.
| Platform | Latest version | CVEs tracked | Last checked |
|---|---|---|---|
| Windows | 1.111 | 11 | 2024-08-27 |
Known vulnerabilities (CVEs) in Microsoft Visual Studio Code
Lavawall tracks 11 published CVEs affecting Microsoft Visual Studio Code, and deploys the versions that fix them automatically across your fleet.
| CVE | Published | Severity | Details | Vector |
|---|---|---|---|---|
| CVE-2026-47282 | 2026-07-14 17:16:49 | MEDIUM (7) | Insufficiently protected credentials in GitHub Copilot and Visual Studio Code allows an unauthorized attacker to disclose information over a network. | NETWORK |
| CVE-2026-45482 | 2026-06-09 17:17:23 | HIGH (8) | Improper limitation of a pathname to a restricted directory ('path traversal') in GitHub Copilot and Visual Studio Code allows an unauthorized attacker to bypass a security feature locally. | LOCAL |
| CVE-2026-41109 | 2026-05-12 18:17:22 | HIGH (9) | Improper neutralization of special elements in output used by a downstream component ('injection') in GitHub Copilot and Visual Studio allows an unauthorized attacker to bypass a security feature over a network. | NETWORK |
| CVE-2026-21523 | 2026-02-10 18:16:35 | HIGH (8) | Time-of-check time-of-use (toctou) race condition in GitHub Copilot and Visual Studio allows an authorized attacker to execute code over a network. | NETWORK |
| CVE-2026-21518 | 2026-02-10 18:16:34 | HIGH (9) | Improper neutralization of special elements used in a command ('command injection') in GitHub Copilot and Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network. | NETWORK |
| CVE-2025-64660 | 2025-11-20 23:15:57 | HIGH (8) | Improper access control in GitHub Copilot and Visual Studio Code allows an authorized attacker to execute code over a network. | NETWORK |
| CVE-2025-62453 | 2025-11-11 18:15:50 | MEDIUM (5) | Improper validation of generative ai output in GitHub Copilot and Visual Studio Code allows an authorized attacker to bypass a security feature locally. | LOCAL |
| CVE-2021-34479 | 2021-07-14 18:15:11 | HIGH (8) | Microsoft Visual Studio Spoofing Vulnerability | LOCAL |
| CVE-2020-16977 | 2020-10-16 23:15:17 | HIGH (7) | <p>A remote code execution vulnerability exists in Visual Studio Code when the Python extension loads a Jupyter notebook file. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.</p> <p>To exploit this vulnerability, an attacker would need to convince a target to open a specially crafted file in Visual Studio Code with the Python extension installed.</p> <p>The update addresses the vulnerability by modifying the way Visual Studio Code Python extension renders notebook content.</p> | LOCAL |
| CVE-2020-1192 | 2020-05-21 23:15:19 | HIGH (8) | A remote code execution vulnerability exists in Visual Studio Code when the Python extension loads workspace settings from a notebook file, aka 'Visual Studio Code Python Extension Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2020-1171. | LOCAL |
| CVE-2020-1171 | 2020-05-21 23:15:18 | HIGH (9) | A remote code execution vulnerability exists in Visual Studio Code when the Python extension loads configuration files after opening a project, aka 'Visual Studio Code Python Extension Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2020-1192. | NETWORK |
Why keeping Microsoft Visual Studio Code 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 Microsoft Visual Studio Code 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 Microsoft Visual Studio Code
Lavawall® watches Microsoft Visual Studio Code 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 Microsoft Visual Studio Code, one policy to bring them current, and timestamped evidence for audits.
Frequently asked questions
Lavawall tracks Microsoft Visual Studio Code at version 1.111 (last checked 2024-08-27). New releases are monitored continuously and can be deployed automatically across your fleet.
Lavawall tracks 11 CVEs for Microsoft Visual Studio Code and remediates them automatically as part of patching.
Deploy the Lavawall® agent and Microsoft Visual Studio Code updates are applied automatically across Windows, macOS, and Linux, risk-ranked and reported, independently of your RMM.
Lavawall® monitors releases and CVEs for Microsoft Visual Studio Code through public information and proprietary statistical analysis, and can patch it automatically across your fleet.