CVE-2020-0604
A remote code execution vulnerability exists in Visual Studio Code when it process environment variables after opening a project.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (3.62%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
A remote code execution vulnerability exists in Visual Studio Code when it process environment variables after opening a project. 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. To exploit this vulnerability, an attacker would need to convince a target to clone a repository and open it in Visual Studio Code. Attacker-specified code would execute when the target opened the integrated terminal. The update address the vulnerability by modifying the way Visual Studio Code handles environment variables.
- CVSS 3.1
- 7.8 HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 3.62% probability · 89th percentile
- Public exploits
- None in Exploit-DB
- CISA KEV
- Not listed
- Affected
- microsoft/visual studio code
- Source
- secure@microsoft.com
EPSS 3.6% since 26 October 2026; no change recorded yet. Points are recorded when the score first appears and whenever it moves by a percentage point or more.
References
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0604Patch, Vendor Advisory
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0604Patch, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.