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

CVE-2020-28426 — kill-process-on-port

HIGH

CVE-2020-28426 is a high-severity (CVSS 7.3) OS Command Injection vulnerability in kill-process-on-port. 1 public exploit reference exists, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Command injection in kill-process-on-port

Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
1 known
Exploitation data as of Oct 14, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.9%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.43%3.09%5.75%8.40%6.9%1.9%Apr 26Aug 26Oct 26

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

How urgent is this, really

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

Where this sits among everything scored

Of 386,684 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.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
kill-process-on-portnpm
6downloads / week

Description

All versions of package kill-process-on-port are vulnerable to Command Injection via a.getProcessPortId.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmkill-process-on-portall versionsNo fix

Affected Products

1 product · 1 configurations
Application
kill-process-on-portkill-process-on-port_project
all
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 package kill-process-on-port are vulnerable to Command I…

snyk.ioNVDJul 2021

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Remediation status

    No patched version of kill-process-on-port has shipped for CVE-2020-28426 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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

All versions of package kill-process-on-port are vulnerable to Command Injection via a.getProcessPortId.
O3 Security · Impact-Aware SCA

Is CVE-2020-28426 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works