Vulnerability Database · npm · tree-kill · Version
tree-kill 0.0.5
0.0.5 is affected by 3 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 1.2.2.
Critical 2 High 1 Medium 0 Low 0 Unrated 0
-
Released 24 Jul 2013
Licence MIT
Also known from other sources 2
Newer releases 13
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
tree-kill 0.0.5 vulnerabilities
3 vulnerabilities cover tree-kill 0.0.5. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Remote Code Execution Vulnerability in tree-kill | 9.8 critical | No fix published | 24 May 2022 |
| CVE-2019-15598: Command Injection in tree-kill | 9.8 critical | 1.2.2 | 24 May 2022 |
| Command Injection in tree-kill | N/A high | 1.2.2 | 04 Sep 2020 |
Looking for another version, or everything Vulert holds for tree-kill?
Questions
About tree-kill 0.0.5
Is tree-kill 0.0.5 vulnerable?
Yes. 3 vulnerabilities in the Vulert database cover tree-kill 0.0.5: 2 critical, 1 high, 0 medium and 0 low. The upgrade Vulert recommends is 1.2.2, and each entry above names the fixed version to move to.
Which version of tree-kill should I use instead of 0.0.5?
1.2.2 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 0.0.5 the latest release of tree-kill?
No. 0.0.5 was published 24 Jul 2013, 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 tree-kill for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the tree-kill version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.