Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

CVE-2020-7781 — connection-tester

CRITICALFix: skoranga/node-connection-tester#10

CVE-2020-7781 is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in connection-tester. 1 public exploit reference exists, so weaponization risk is real. A fix is available for connection-tester — see the affected versions and patch details below.

Command injection in connection-tester

Also known asGHSA-w5mp-8p8w-mhh8SNYK-JS-CONNECTIONTESTER-1048337
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk
0.06%0.87%1.68%2.49%0.6%2.0%Apr 26Aug 26Oct 26

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

How urgent is this, really

CVE-2020-7781 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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.

8other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
connection-testernpm
767downloads / week

Description

This affects the package connection-tester before 0.2.1. The injection point is located in line 15 in index.js. Affected versions of this package are vulnerable to Command Injection

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmconnection-testerall versions0.2.1npm install connection-tester@0.2.1

Affected Products

1 product · 1 configurations
Application
connection-testerconnection-tester_project
< 0.2.1
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.

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update connection-tester to 0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-7781 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

This affects the package connection-tester before 0.2.1. The injection point is located in line 15 in index.js. Affected versions of this package are vulnerable to Command Injection
O3 Security · Impact-Aware SCA

Is CVE-2020-7781 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2020-7781: connection — Fixed in 0.2.1