VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

yargs-parser: vulnerability history, versions and safety

yargs-parser is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 18 releases, first recorded in Sep 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all yargs-parser vulnerabilities

Vulert verdict on yargs-parser 22.0.0 i

Updated on 23 Oct 2026

Good news: 22.0.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 77/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Quiet

What to do: Stay on 22.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 22.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 22.0.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 04 Sep 2020 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Depended on by 11,455 packages i
  • Stars 520 i
  • OpenSSF scorecard 3/10 i
  • Last release 16 months ago i
  • Licence ISC i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for yargs-parser, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
22.0.0 26 May 2025 none ISC — Details →
21.1.1 04 Aug 2022 none ISC — Details →
21.1.0 03 Aug 2022 none ISC — Details →
21.0.1 27 Feb 2022 none ISC — Details →
21.0.0 16 Nov 2021 none ISC — Details →
20.2.9 20 Jun 2021 none ISC — Details →
15.0.3 20 Jun 2021 none ISC — Details →
15.0.2 20 Jun 2021 none ISC — Details →
20.2.7 10 Mar 2021 none ISC — Details →
5.0.1 10 Mar 2021 none ISC — Details →
20.2.6 22 Feb 2021 none ISC — Details →
20.2.5 13 Feb 2021 none ISC — Details →
20.2.4 09 Nov 2020 none ISC — Details →
20.2.3 16 Oct 2020 none ISC — Details →
20.2.2 14 Oct 2020 none ISC — Details →
20.2.1 01 Oct 2020 none ISC — Details →
20.2.0 21 Sep 2020 none ISC — Details →
20.1.0 20 Sep 2020 none ISC — Details →
20.0.0 09 Sep 2020 none ISC — Details →
19.0.4 27 Aug 2020 none ISC — Details →
19.0.1 09 Aug 2020 none ISC — Details →
19.0.0 09 Aug 2020 none ISC — Details →
19.0.0-beta.3 06 Aug 2020 none ISC — Details →
19.0.0-beta.2 04 Aug 2020 none ISC — Details →
19.0.0-beta.1 19 Jul 2020 none ISC — Details →
19.0.0-beta.0 19 Jul 2020 none ISC — Details →
5.0.0-security.0 22 May 2020 none ISC — Details →
18.1.3 16 Apr 2020 none ISC — Details →
18.1.2 26 Mar 2020 none ISC — Details →
18.1.1 16 Mar 2020 none ISC — Details →
13.1.2 13 Mar 2020 none ISC — Details →
15.0.1 13 Mar 2020 none ISC — Details →
18.1.1-beta.0 12 Mar 2020 none ISC — Details →
18.1.0 07 Mar 2020 none ISC — Details →
18.0.0 02 Mar 2020 none ISC — Details →
17.1.0 01 Mar 2020 none ISC — Details →
17.0.1 29 Feb 2020 none ISC — Details →
17.0.0 10 Feb 2020 none ISC — Details →
16.1.0 01 Nov 2019 none ISC — Details →
16.0.0 27 Oct 2019 none ISC — Details →
15.0.0 07 Oct 2019 none ISC — Details →
14.0.0 06 Sep 2019 none ISC — Details →
13.1.1 10 Jun 2019 M1 ISC Yes Details →
13.1.0 05 May 2019 M1 ISC Yes Details →
13.0.0 02 Feb 2019 M1 ISC Yes Details →
13.0.0-candidate.0 02 Feb 2019 M1 ISC Yes Details →
12.0.0 29 Jan 2019 M1 ISC Yes Details →
11.1.1 19 Nov 2018 M1 ISC Yes Details →
11.1.0 10 Nov 2018 M1 ISC Yes Details →
11.0.0 06 Oct 2018 M1 ISC Yes Details →
10.1.0 29 Jun 2018 M1 ISC Yes Details →
10.0.0 04 Apr 2018 M1 ISC Yes Details →
9.0.2 20 Jan 2018 M1 ISC Yes Details →
9.0.1 20 Jan 2018 M1 ISC Yes Details →
9.0.0 20 Jan 2018 M1 ISC Yes Details →
8.1.0 20 Dec 2017 M1 ISC Yes Details →
8.0.0 05 Oct 2017 M1 ISC Yes Details →
7.0.0 02 May 2017 M1 ISC Yes Details →
6.0.1 01 May 2017 M1 ISC Yes Details →
6.0.0 01 May 2017 M1 ISC Yes Details →
5.0.0 18 Feb 2017 none ISC — Details →
4.2.1-candidate.1 06 Jan 2017 none ISC — Details →
4.2.1-candidate.0 06 Jan 2017 none ISC — Details →
4.2.1 02 Jan 2017 none ISC — Details →
4.2.0 01 Dec 2016 none ISC — Details →
4.1.0 07 Nov 2016 none ISC — Details →
4.0.2 30 Sep 2016 none ISC — Details →
4.0.1 30 Sep 2016 none ISC — Details →
4.0.0 26 Sep 2016 none ISC — Details →
3.2.0 13 Aug 2016 none ISC — Details →
3.1.0 09 Aug 2016 none ISC — Details →
2.4.1 16 Jul 2016 none ISC — Details →
2.4.0 11 Apr 2016 none ISC — Details →
2.4.0-next 11 Apr 2016 none ISC — Details →
2.2.0 30 Mar 2016 none ISC — Details →
2.1.2 20 Mar 2016 none ISC — Details →
2.1.1 23 Feb 2016 none ISC — Details →
2.1.0 14 Feb 2016 none ISC — Details →
2.0.0 06 Feb 2016 none ISC — Details →
1.1.1-alpha3 01 Feb 2016 none ISC — Details →
1.1.1-alpha2 30 Jan 2016 none ISC — Details →
1.1.1-alpha 29 Jan 2016 none ISC — Details →
1.1.0 24 Jan 2016 none ISC — Details →
1.0.0 23 Jan 2016 none ISC — Details →

All 84 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for yargs-parser

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 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

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About yargs-parser

Is yargs-parser safe to use?

Vulert records 1 vulnerabilities for yargs-parser in npm: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is yargs-parser's Vulert package health score?

Vulert scores yargs-parser 77/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of yargs-parser affected?

No. 22.0.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of yargs-parser should I use?

22.0.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does yargs-parser have?

1 vulnerability is recorded for yargs-parser in the npm ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new yargs-parser vulnerabilities disclosed?

0 vulnerabilities were recorded for yargs-parser in the last 12 months, and the oldest entry in this database dates to 04 Sep 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of yargs-parser are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.