How severe is CVE-2021-26700?

No CVSS score has been assigned to CVE-2021-26700 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2021-26700?

CVE-2021-26700 affects the following packages: vscode-npm-script (npm). Ecosystems affected: npm.

How do I fix CVE-2021-26700?

The records we use list no patched version of vscode-npm-script for CVE-2021-26700. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2021-26700 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vscode-npm-script, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-26700 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2021-26700 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2021-26700, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2021-26700?

CVE-2021-26700 has an EPSS (Exploit Prediction Scoring System) score of 6.0%, placing it in the 93th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2021-26700 published, and has it been updated?

CVE-2021-26700 was published on May 24, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2021-26700 — vscode-npm-script

CVE-2021-26700 is a remote code execution vulnerability in vscode-npm-script. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Remote code execution in vscode-npm-script

Published

May 24, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

See advisory

Exploits

2 known

Exploitation data as of Oct 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

6.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

vscode-npm-scriptnpm

5downloads / week

Description

Visual Studio Code npm-script Extension Remote Code Execution Vulnerability

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`vscode-npm-script`	≥ 0.0.0	No fix

Affected Products

1 product · 1 configurations

Application

npmmicrosoft

< 0.3.15

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Visual Studio Code npm-script Extension Remote Code Execution Vulnerabil…

github.comGithubFeb 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vscode-npm-script, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of vscode-npm-script for CVE-2021-26700. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Visual Studio Code npm-script Extension Remote Code Execution Vulnerability

O3 Security · Impact-Aware SCA

Is CVE-2021-26700 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works