# CVE-2020-1171: Visual Studio Code Python Extension Remote Code Execution Vulnerability

> Attackers can execute arbitrary code by tricking users into opening a malicious project in VS Code with the Python extension installed.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 May 2020
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-v7q9-qwmc-9665

## What is CVE-2020-1171?

CVE-2020-1171 is a high-severity code injection vulnerability in Microsoft Python extension for Visual Studio Code, published on 21 May 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A remote code execution vulnerability exists in Visual Studio Code when the Python extension loads configuration files 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 with the Python extension installed. Attacker-specified code would execute when the target opened the integrated terminal.
The update address the vulnerability by modifying the way Visual Studio Code Python extension handles environment variables.

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

It affects 1 product.


Products: Microsoft Python.

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

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

## Is CVE-2020-1171 being exploited?

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

## Other vulnerabilities in Microsoft Python extension for Visual Studio Code

- [CVE-2024-49050](https://insights.sbomify.com/CVE-2024-49050/): Visual Studio Code Python Extension Remote Code Execution Vulnerability (high 8.8)
- [CVE-2026-54981](https://insights.sbomify.com/CVE-2026-54981/): Visual Studio Code Python Extension Security Feature Bypass Vulnerability (high 7.8)
- [CVE-2025-49714](https://insights.sbomify.com/CVE-2025-49714/): Visual Studio Code Python Extension Remote Code Execution Vulnerability (high 7.8)
- [CVE-2020-17163](https://insights.sbomify.com/CVE-2020-17163/): Visual Studio Code Python Extension Remote Code Execution Vulnerability (high 7.8)
- [CVE-2020-1192](https://insights.sbomify.com/CVE-2020-1192/): Visual Studio Code Python Extension Remote Code Execution Vulnerability (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-1171 is a high-severity code injection vulnerability in Microsoft Python extension for Visual Studio Code, published on 21 May 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-1171 in the wild and no public exploit code.

Affected product: Microsoft Python extension for Visual Studio Code. 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-1171/ (Markdown: https://insights.sbomify.com/CVE-2020-1171/index.md)
```

## Sources

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

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