VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

plist: vulnerability history, versions and safety

plist is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 23 releases, first recorded in Feb 2022. 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 C1
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 plist vulnerabilities

Vulert verdict on plist 5.0.0 i

Updated on 22 Oct 2026

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

Package health score 72/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 5.0.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 18 Feb 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 244 packages i
  • Stars 606 i
  • OpenSSF scorecard 2/10 i
  • Last release 5 months ago i
  • Licence MIT 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 plist, 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
5.0.0 03 May 2026 none MIT — Details →
4.0.0 25 Apr 2026 none MIT — Details →
3.1.1 25 Apr 2026 none MIT — Details →
3.1.0 06 Jul 2023 none MIT — Details →
3.0.6 12 Jul 2022 none MIT — Details →
3.0.5 23 Mar 2022 none MIT — Details →
3.0.4 27 Aug 2021 C1 MIT Yes Details →
3.0.3 04 Aug 2021 C1 MIT Yes Details →
3.0.2 26 Mar 2021 C1 MIT Yes Details →
3.0.1 21 Mar 2018 C1 MIT Yes Details →
3.0.0 18 Mar 2018 C1 MIT Yes Details →
2.1.0 04 May 2017 C1 MIT Yes Details →
2.0.1 16 Aug 2016 C1 MIT Yes Details →
2.0.0 16 Aug 2016 C1 MIT Yes Details →
1.2.0 10 Nov 2015 C1 MIT Yes Details →
1.1.0 28 Aug 2014 C1 MIT Yes Details →
1.0.1 25 Jun 2014 C1 MIT Yes Details →
1.0.0 21 May 2014 C1 MIT Yes Details →
0.4.3 19 Feb 2013 C1 MIT Yes Details →
0.4.2 30 Jan 2013 C1 MIT Yes Details →
0.4.1 16 Nov 2012 C1 MIT Yes Details →
0.4.0 01 Oct 2012 C1 MIT Yes Details →
0.3.3 29 Sep 2012 C1 MIT Yes Details →
0.3.2 29 Sep 2012 C1 MIT Yes Details →
0.3.1 27 Sep 2012 C1 MIT Yes Details →
0.2.1 06 Nov 2011 C1 MIT Yes Details →
0.2.0 03 Jun 2011 C1 MIT Yes Details →
0.1.0 06 May 2011 C1 MIT Yes Details →
0.1.1 06 May 2011 C1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 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 plist

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-22912: Prototype pollution in Plist before 3.0.5 can cause denial of service 9.8 critical 3.0.5 18 Feb 2022

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 →

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.

Add Vulert as a Preferred Source

Questions

About plist

Is plist safe to use?

Vulert records 1 vulnerabilities for plist in npm: 1 critical, 0 high, 0 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 plist's Vulert package health score?

Vulert scores plist 72/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 plist affected?

No. 5.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 plist should I use?

5.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 plist have?

1 vulnerability is recorded for plist in the npm ecosystem: 1 critical, 0 high, 0 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 plist vulnerabilities disclosed?

0 vulnerabilities were recorded for plist in the last 12 months, and the oldest entry in this database dates to 18 Feb 2022. 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 plist 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 plist for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the plist version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.