Vulnerability Database · npm · yargs-parser · Version
yargs-parser 13.0.0-candidate.0
13.0.0-candidate.0 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: 22.0.0.
Critical 0 High 0 Medium 1 Low 0 Unrated 0
-
Released 02 Feb 2019
Licence ISC
Also known from other sources 1
Newer releases 84
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
yargs-parser 13.0.0-candidate.0 vulnerabilities
1 vulnerability cover yargs-parser 13.0.0-candidate.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2020-7608: yargs-parser Vulnerable to Prototype Pollution | 5.3 medium | 13.1.2 | 04 Sep 2020 |
Looking for another version, or everything Vulert holds for yargs-parser?
Questions
About yargs-parser 13.0.0-candidate.0
Is yargs-parser 13.0.0-candidate.0 vulnerable?
Yes. 1 vulnerability in the Vulert database cover yargs-parser 13.0.0-candidate.0: 0 critical, 0 high, 1 medium and 0 low. The upgrade Vulert recommends is 22.0.0, and each entry above names the fixed version to move to.
Which version of yargs-parser should I use instead of 13.0.0-candidate.0?
22.0.0 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 13.0.0-candidate.0 the latest release of yargs-parser?
No. 13.0.0-candidate.0 was published 02 Feb 2019, 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 yargs-parser for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the yargs-parser version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.