NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

CVE-2020-7645 — chrome-launcher

CRITICALFix: GoogleChrome/chrome-launcher#197

CVE-2020-7645 is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in chrome-launcher. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for chrome-launcher — see the affected versions and patch details below.

chrome-launcher subject to OS Command Injection

Also known asGHSA-gp2j-mg4w-2rh5SNYK-JS-CHROMELAUNCHER-537575
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs64th percentile — riskier than 64% of all scored CVEsHighest risk
0.08%0.57%1.06%1.55%0.6%1.0%Apr 26Aug 26Oct 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

843other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
chrome-launchernpm
13.5Mdownloads / week

Description

chrome-launcher prior to 0.13.2 is subject to OS Command Injection via the $HOME environment variable in Linux operating systems. This issue is patched in version 0.13.2.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmchrome-launcherall versions0.13.2npm install chrome-launcher@0.13.2

Affected Products

1 product · 1 configurations
Application
chrome-launchergoogle
< 0.13.2
range
Exploits & PoCs
1

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

All versions of chrome-launcher allow execution of arbitrary commands, b…

snyk.ioNVDMay 2020

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update chrome-launcher to 0.13.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-7645 is resolved across your whole dependency graph.

  3. Workarounds

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

chrome-launcher prior to 0.13.2 is subject to OS Command Injection via the `$HOME` environment variable in Linux operating systems. This issue is patched in version 0.13.2.
O3 Security · Impact-Aware SCA

Is CVE-2020-7645 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-7645: chrome — Fixed in 0.13.2