Vulnerability Database · npm · pidusage · Version
pidusage 1.0.0
1.0.0 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 2 High 0 Medium 0 Low 0 Unrated 0
-
Released 17 Dec 2015
Licence MIT
Also known from other sources 2
Newer releases 53
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
pidusage 1.0.0 vulnerabilities
2 vulnerabilities cover pidusage 1.0.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2017-1000220: PIDUsage Enables OS Command Injection in pidusage | 9.8 critical | 1.1.5 | 13 May 2022 |
| CVE-2017-16034: Command Injection in pidusage | N/A critical | 1.1.5 | 01 Sep 2020 |
Looking for another version, or everything Vulert holds for pidusage?
Questions
About pidusage 1.0.0
Is pidusage 1.0.0 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover pidusage 1.0.0: 2 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 1.0.0 the latest release of pidusage?
No. 1.0.0 was published 17 Dec 2015, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor pidusage for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the pidusage version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.