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. O3 Security confirms whether GHSA-63m4-fhf2-cmf7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Command Execution in windows-cpu
Real-World Exposure
windows-cpuReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | windows-cpu | all versions | 0.1.5 |
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 dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for windows-cpu. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-63m4-fhf2-cmf7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-63m4-fhf2-cmf7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-63m4-fhf2-cmf7 in your dependencies?
O3 detects GHSA-63m4-fhf2-cmf7 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.