# CVE-2021-26700: Visual Studio Code npm-script Extension Remote Code Execution Vulnerability

> An attacker can execute arbitrary code via the npm-script extension in Visual Studio Code, requiring users to update the extension.

- **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:** 25 Feb 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-r84v-qff8-jv5g

## What is CVE-2021-26700?

CVE-2021-26700 is a high-severity code injection vulnerability in Microsoft Visual Studio Code - npm-script Extension, published on 25 Feb 2021. 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 npm-script Extension Remote Code Execution Vulnerability

## Which versions are affected by CVE-2021-26700?

2 open source packages ship an affected version, including vscode-npm-script. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vscode-npm-script` | npm | From 0.0.0 | None |
| `vscode-npm-script` | npm | From 0.0.0 | None |

Products: Microsoft Npm.

## How do I fix CVE-2021-26700?

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

## Is CVE-2021-26700 being exploited?

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

Public exploit code:

- RCE in NPM VSCode Extension (github_poc): https://github.com/jackadamson/CVE-2021-26700
- https://github.com/june-in-exile/CVE-2021-26700 (github_poc): https://github.com/june-in-exile/CVE-2021-26700

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-26700 and fix it if it is affected.

What it is: CVE-2021-26700 is a high-severity code injection vulnerability in Microsoft Visual Studio Code - npm-script Extension, published on 25 Feb 2021. 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-2021-26700 in the wild and no public exploit code.

Affected packages and fixed versions:
- vscode-npm-script (npm): affected from 0.0.0; no fix listed
- vscode-npm-script (npm): affected from 0.0.0; no fix listed

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-2021-26700/ (Markdown: https://insights.sbomify.com/CVE-2021-26700/index.md)
```

## Sources

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

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