Vulnerability Database · npm · babelcli · Version
babelcli 0.0.2-security
0.0.2-security is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 1.0.0.
Critical 0 High 1 Medium 0 Low 0 Unrated 0
-
Released 02 Aug 2017
Status latest release
Also known from other sources 1
Newer releases 3
Database updated 22/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
babelcli 0.0.2-security vulnerabilities
1 vulnerability cover babelcli 0.0.2-security. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2017-16060: Hijacked Environment Variables in babelcli | 7.5 high | No fix published | 29 Aug 2018 |
Looking for another version, or everything Vulert holds for babelcli?
Questions
About babelcli 0.0.2-security
Is babelcli 0.0.2-security vulnerable?
Yes. 1 vulnerability in the Vulert database cover babelcli 0.0.2-security: 0 critical, 1 high, 0 medium and 0 low. The upgrade Vulert recommends is 1.0.0, and each entry above names the fixed version to move to.
Which version of babelcli should I use instead of 0.0.2-security?
1.0.0 is the version Vulert recommends for this release line, which is also the release the publisher currently ships. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 0.0.2-security the latest release of babelcli?
Yes. 0.0.2-security is the current release, published 02 Aug 2017. Staying on the current line is what keeps you inside the publisher's fixes.
How do I monitor babelcli for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the babelcli version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.