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

CVE-2019-15609 — kill-port-process

CRITICAL

CVE-2019-15609 is a critical-severity (CVSS 9.8) CWE-77 vulnerability in kill-port-process. 1 public exploit reference exists, so weaponization risk is real. A fix is available for kill-port-process — see the affected versions and patch details below.

OS Command Injection and Command Injection in kill-port-process

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

EPSS Exploitation Probability

via FIRST.org ↗
4.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk
3.41%4.10%4.80%5.50%5.0%4.0%Apr 26Aug 26Oct 26

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

How urgent is this, really

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

Where this sits among everything scored

Of 385,738 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.

18other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
kill-port-processnpm
103Kdownloads / week

Description

The kill-port-process package version < 2.2.0 is vulnerable to a Command Injection vulnerability.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmkill-port-processall versions2.2.0npm install kill-port-process@2.2.0

Affected Products

1 product · 1 configurations
Application
kill-port-processkill-port-process_project
< 2.2.0
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.

The kill-port-process package version < 2.2.0 is vulnerable to a Command…

hackerone.comNVDMar 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 kill-port-process, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update kill-port-process to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-15609 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

The kill-port-process package prior to version 2.2.0 is vulnerable to a Command Injection.
O3 Security · Impact-Aware SCA

Is CVE-2019-15609 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2019-15609: kill-port — Fixed in 2.2.0