visual_studio_code is a software product developed by microsoft, a major technology provider with a global presence in enterprise and consumer markets. This product is widely deployed in production environments, making vulnerability monitoring essential for organizations relying on it. Security vulnerabilities in products of this category can affect system availability, data confidentiality, and integrity across entire networks. The significant number of reported vulnerabilities indicates this product has received substantial security scrutiny and community focus over time. Regular assessment of known vulnerabilities and timely patching are fundamental components of responsible system administration for any deployment of this software.
SecUtils has identified 52 known vulnerabilities affecting microsoft visual_studio_code. This includes 45 high-severity issues requiring prompt remediation. Vulnerabilities in this product have been disclosed spanning from 2018 to 2026, indicating a sustained research interest and ongoing security attention. 7 medium-severity issues complete the vulnerability landscape. Organizations should prioritize patching based on deployment context, asset criticality, and exploitation likelihood rather than severity alone.
| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2018-0597 | 2018-06-26 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2019-0728 | 2019-03-05 | 2024-11-21 | 7.8 | 9.3 | Likely |
| CVE-2019-1414 | 2020-01-24 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2020-1416 | 2020-07-14 | 2024-11-21 | 8.8 | 9.3 | Likely |
| CVE-2020-0604 | 2020-08-17 | 2026-02-23 | 7.8 | 9.3 | Likely |
| CVE-2020-16881 | 2020-09-11 | 2026-02-23 | 7.8 | 9.3 | Likely |
| CVE-2020-16977 | 2020-10-16 | 2026-02-23 | 7.0 | 9.3 | Likely |
| CVE-2020-17023 | 2020-10-16 | 2026-02-23 | 7.8 | 9.3 | Likely |
| CVE-2020-17104 | 2020-11-11 | 2024-11-21 | 7.8 | 9.3 | Likely |
| CVE-2020-17148 | 2020-12-10 | 2025-08-28 | 7.8 | 6.8 | Likely |
| CVE-2021-1639 | 2021-02-25 | 2024-11-21 | 7.0 | 6.8 | Likely |
| CVE-2021-27060 | 2021-03-11 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2021-28457 | 2021-04-13 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2021-28469 | 2021-04-13 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2021-28471 | 2021-04-13 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2021-28473 | 2021-04-13 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2021-28475 | 2021-04-13 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2021-28477 | 2021-04-13 | 2024-11-21 | 7.0 | 6.8 | Likely |
| CVE-2021-31211 | 2021-05-11 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2021-31214 | 2021-05-11 | 2024-11-21 | 7.8 | 9.3 | Likely |
| CVE-2021-34479 | 2021-07-14 | 2024-11-21 | 7.8 | 4.3 | Likely |
| CVE-2021-34528 | 2021-07-14 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2021-34529 | 2021-07-14 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2021-26437 | 2021-09-15 | 2024-11-21 | 5.5 | 4.3 | Likely |
| CVE-2021-42322 | 2021-11-10 | 2024-11-21 | 7.8 | 4.6 | Unknown |
| CVE-2021-43891 | 2021-12-15 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2021-43908 | 2021-12-15 | 2024-11-21 | 4.3 | 4.3 | Likely |
| CVE-2022-21991 | 2022-02-09 | 2024-11-21 | 8.1 | 6.8 | Likely |
| CVE-2022-24526 | 2022-03-09 | 2024-11-21 | 6.1 | 4.3 | Likely |
| CVE-2022-26921 | 2022-04-15 | 2024-11-21 | 7.3 | 4.6 | Unknown |
| CVE-2022-30129 | 2022-05-10 | 2025-01-02 | 8.8 | 6.8 | Likely |
| CVE-2022-38020 | 2022-09-13 | 2024-11-21 | 7.3 | - | - |
| CVE-2022-41034 | 2022-10-11 | 2025-01-02 | 7.8 | - | - |
| CVE-2022-41042 | 2022-10-11 | 2025-01-02 | 7.4 | - | - |
| CVE-2023-21779 | 2023-01-10 | 2024-11-21 | 7.8 | - | - |
| CVE-2023-24893 | 2023-04-11 | 2024-11-21 | 7.8 | - | - |
| CVE-2023-29338 | 2023-05-09 | 2024-11-21 | 6.6 | - | - |
| CVE-2023-33144 | 2023-06-14 | 2024-11-21 | 6.6 | - | - |
| CVE-2023-36742 | 2023-09-12 | 2024-11-21 | 7.8 | - | - |
| CVE-2024-26165 | 2024-03-12 | 2024-12-27 | 8.8 | - | - |
| CVE-2024-43488 | 2024-10-08 | 2024-10-21 | 8.8 | - | - |
| CVE-2024-43601 | 2024-10-08 | 2024-11-08 | 7.8 | - | - |
| CVE-2025-24039 | 2025-02-11 | 2025-07-02 | 7.3 | - | - |
| CVE-2025-24042 | 2025-02-11 | 2025-07-02 | 7.3 | - | - |
| CVE-2025-26631 | 2025-03-11 | 2025-07-03 | 7.3 | - | - |
| CVE-2025-32726 | 2025-04-12 | 2025-07-08 | 6.8 | - | - |
| CVE-2025-21264 | 2025-05-13 | 2025-05-19 | 7.1 | - | - |
| CVE-2025-55319 | 2025-09-12 | 2026-02-20 | 8.8 | - | - |
| CVE-2025-62453 | 2025-11-11 | 2025-11-14 | 5.0 | - | - |
| CVE-2025-64660 | 2025-11-20 | 2025-11-26 | 8.0 | - | - |
| CVE-2026-21518 | 2026-02-10 | 2026-02-23 | 8.8 | - | - |
| CVE-2026-21523 | 2026-02-10 | 2026-02-11 | 8.0 | - | - |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records for microsoft visual_studio_code by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and structuring the data for rapid analysis and asset correlation. For every vulnerability listed, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference information to enable organizations to prioritize patching and risk assessment efficiently. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for vulnerability management and security operations.