# CVE-2020-17150: Visual Studio Code Remote Code Execution Vulnerability

> Attackers can execute arbitrary code via the Visual Studio Code TS-Lint extension, requiring developers to apply the vendor patch.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Dec 2020
- **Updated:** 9 Jun 2026
- **Also known as:** GHSA-g2h3-68xr-m8j6

## What is CVE-2020-17150?

CVE-2020-17150 is a high-severity code injection vulnerability in Microsoft Visual Studio Code TS-Lint Extension, published on 9 Dec 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Visual Studio Code Remote Code Execution Vulnerability

## Which versions are affected by CVE-2020-17150?

It affects 1 product.


Products: Microsoft Tslint.

## How do I fix CVE-2020-17150?

No fix has been published for CVE-2020-17150 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-17150 being exploited?

There is no known exploitation of CVE-2020-17150 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-17150 and fix it if it is affected.

What it is: CVE-2020-17150 is a high-severity code injection vulnerability in Microsoft Visual Studio Code TS-Lint Extension, published on 9 Dec 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-17150 in the wild and no public exploit code.

Affected product: Microsoft Visual Studio Code TS-Lint Extension. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-17150/ (Markdown: https://insights.sbomify.com/CVE-2020-17150/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-17150
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-17150
- OSV: https://osv.dev/vulnerability/CVE-2020-17150

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-17150/
Summaries are generated and may contain mistakes; the official description above is the record.