Visual Studio Code vulnerabilitiesRanked by how likely they are to be used.
Visual Studio Code is made by Microsoft. We track 50 published vulnerabilities listed under that exact name, across 633 versions. None of them is on the list of flaws known to be exploited today. Microsoft lists newer releases under their own names, such as Visual Studio Code Eslint Extension, so check those pages too.
We keep watching the known-exploited list.
Is Visual Studio Code listed under other names? Yes.
Microsoft also lists Visual Studio Code under more specific names, such as Visual Studio Code Eslint Extension and Visual Studio Code Github Pull Requests and Issues. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Visual Studio Code vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Visual Studio Code's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Visual Studio Code flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 67%CVE-2022-41034High
Visual Studio Code Remote Code Execution Vulnerability
- 62%CVE-2021-27084High
Visual Studio Code Java Extension Pack Remote Code Execution Vulnerability
- 41%CVE-2022-30129High
Visual Studio Code Remote Code Execution Vulnerability
- 28%CVE-2019-0728High
A remote code execution vulnerability exists in Visual Studio Code when it process environment variables after opening a project, aka 'Visual Studio Code Remote Code Execution Vulnerability'.
- 14%CVE-2021-43891High
Visual Studio Code Remote Code Execution Vulnerability
- 5.9%CVE-2020-1416High
An elevation of privilege vulnerability exists in Visual Studio and Visual Studio Code when they load software dependencies, aka 'Visual Studio and Visual Studio Code Elevation of Privilege Vulnerability'.
- 5.6%CVE-2018-0597High
Untrusted search path vulnerability in the installer of Visual Studio Code allows an attacker to gain privileges via a Trojan horse DLL in an unspecified directory.
- 5.4%CVE-2020-16881High
<p>A remote code execution vulnerability exists in Visual Studio Code when a user is tricked into opening a malicious 'package.json' file.
- 5.2%CVE-2020-1171High
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...
- 5.1%CVE-2021-34529High
Visual Studio Code Remote Code Execution Vulnerability
Running Visual Studio Code? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Visual Studio Code Remote Code Execution Vulnerability
- Matched to
- Visual Studio Code on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 50 published vulnerabilities listed under the name Visual Studio Code, across 633 versions.
None of Visual Studio Code's vulnerabilities is on the list of flaws known to be exploited today.
Microsoft also lists Visual Studio Code under more specific names, such as Visual Studio Code Eslint Extension and Visual Studio Code Github Pull Requests and Issues. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Visual Studio Code. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.