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

Command Execution in windows-cpuGHSA-63m4-fhf2-cmf7

CRITICALFix: KyleRoss/windows-cpu@b75e19a

GHSA-63m4-fhf2-cmf7 is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in windows-cpu. 1 public exploit reference exists, so weaponization risk is real. A fix is available for windows-cpu — see the affected versions and patch details below.

Also known asCVE-2017-1000219
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.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk
2.84%3.47%4.10%4.74%3.3%4.2%Apr 26Aug 26Oct 26

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

How urgent is this, really

GHSA-63m4-fhf2-cmf7 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.

9other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
windows-cpunpm
2Kdownloads / week

Description

Version of windows-cpu before 0.1.5 will execute arbitrary code passed into the first argument of the findLoad method, resulting in remote code execution.

Proof of Concept

var win = require('windows-cpu');
wind.findLoad('foo & calc.exe');

Recommendation

Update to version 0.1.5 or later.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmwindows-cpuall versions0.1.5npm install windows-cpu@0.1.5

Affected Products

1 product · 2 configurations
Application
windows-cpuwindows-cpu_project
2 versions
0.1.10.1.2
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.

npm/KyleRoss windows-cpu all versions vulnerable to command injection re…

nodesecurity.ioNVDOct 2019

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update windows-cpu to 0.1.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-63m4-fhf2-cmf7 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

Version of `windows-cpu` before 0.1.5 will execute arbitrary code passed into the first argument of the `findLoad` method, resulting in remote code execution. ## Proof of Concept ```js var win = require('windows-cpu'); wind.findLoad('foo & calc.exe'); ``` ## Recommendation Update to version 0.1.5 or later.
O3 Security · Impact-Aware SCA

Is GHSA-63m4-fhf2-cmf7 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Command Execution in windows-cpu (Critical 9.8)