VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

pm2: vulnerability history, versions and safety

pm2 is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in Jun 2025. 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 L1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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 pm2 vulnerabilities

Vulert verdict on pm2 7.1.0 i

Updated on 23 Oct 2026

Careful: 7.1.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 7.1.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 09 Jun 2025 i
  • Highest CVSS 4.3 i
  • With no published fix 1 i
  • Stars 43,312 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence AGPL-3.0 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 pm2, 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
7.1.0 21 Oct 2026 L1 AGPL-3.0 No Details →
7.0.4 24 Aug 2026 L1 AGPL-3.0 No Details →
7.0.3 29 Jun 2026 L1 AGPL-3.0 No Details →
7.0.2 29 Jun 2026 L1 AGPL-3.0 No Details →
7.0.1 02 May 2026 L1 AGPL-3.0 No Details →
7.0.0 02 May 2026 L1 AGPL-3.0 No Details →
6.0.14 26 Nov 2025 L1 AGPL-3.0 No Details →
6.0.13 22 Sep 2025 L1 AGPL-3.0 No Details →
6.0.12 22 Sep 2025 L1 AGPL-3.0 No Details →
6.0.11 15 Sep 2025 L1 AGPL-3.0 No Details →
6.0.10 02 Sep 2025 L1 AGPL-3.0 No Details →
6.0.9 01 Sep 2025 L1 AGPL-3.0 No Details →
6.0.8 05 Jun 2025 L1 AGPL-3.0 No Details →
6.0.7 05 Jun 2025 L1 AGPL-3.0 No Details →
6.0.6 13 May 2025 L1 AGPL-3.0 No Details →
6.0.5 15 Mar 2025 L1 AGPL-3.0 No Details →
5.4.3 13 Nov 2024 L1 AGPL-3.0 No Details →
6.0.0-beta.0 13 Nov 2024 L1 AGPL-3.0 No Details →
5.4.2 08 Jul 2024 L1 AGPL-3.0 No Details →
5.4.1 18 Jun 2024 L1 AGPL-3.0 No Details →
5.4.0 24 May 2024 L1 AGPL-3.0 No Details →
5.3.1 20 Jan 2024 L1 AGPL-3.0 No Details →
5.3.0 15 Mar 2023 L1 AGPL-3.0 No Details →
5.2.2 13 Oct 2022 L1 AGPL-3.0 No Details →
5.2.1 13 Oct 2022 L1 AGPL-3.0 No Details →
5.2.0 17 Feb 2022 L1 AGPL-3.0 No Details →
5.1.2 24 Sep 2021 L1 AGPL-3.0 No Details →
5.1.1 19 Aug 2021 L1 AGPL-3.0 No Details →
5.1.0 10 Jun 2021 L1 AGPL-3.0 No Details →
5.0.4 08 Jun 2021 L1 AGPL-3.0 No Details →
5.0.3 08 Jun 2021 L1 AGPL-3.0 No Details →
5.0.2 08 Jun 2021 L1 AGPL-3.0 No Details →
5.0.1 08 Jun 2021 L1 AGPL-3.0 No Details →
5.0.0 07 Jun 2021 L1 AGPL-3.0 No Details →
4.5.6 01 Apr 2021 L1 AGPL-3.0 No Details →
4.5.5 25 Feb 2021 L1 AGPL-3.0 No Details →
4.5.4 31 Jan 2021 L1 AGPL-3.0 No Details →
4.5.3 31 Jan 2021 L1 AGPL-3.0 No Details →
4.5.2 29 Jan 2021 L1 AGPL-3.0 No Details →
4.5.1 16 Dec 2020 L1 AGPL-3.0 No Details →
4.5.0 29 Sep 2020 L1 AGPL-3.0 No Details →
4.4.1 17 Aug 2020 L1 AGPL-3.0 No Details →
4.4.0 23 Apr 2020 L1 AGPL-3.0 No Details →
4.3.1 20 Apr 2020 L1 AGPL-3.0 No Details →
4.3.0 18 Apr 2020 L1 AGPL-3.0 No Details →
4.2.3 21 Jan 2020 L1 AGPL-3.0 No Details →
4.2.2 20 Jan 2020 L1 AGPL-3.0 No Details →
4.2.1 10 Dec 2019 L1 AGPL-3.0 No Details →
3.5.2 10 Dec 2019 L1 AGPL-3.0 No Details →
4.2.0 25 Nov 2019 L1 AGPL-3.0 No Details →
4.1.2 15 Oct 2019 L1 AGPL-3.0 No Details →
4.1.1 15 Oct 2019 L1 AGPL-3.0 No Details →
4.1.0 15 Oct 2019 L1 AGPL-3.0 No Details →
4.0.2 15 Oct 2019 L1 AGPL-3.0 No Details →
4.0.1 14 Oct 2019 L1 AGPL-3.0 No Details →
4.0.0 11 Oct 2019 L1 AGPL-3.0 No Details →
3.5.1 23 May 2019 L1 AGPL-3.0 No Details →
3.5.0 08 Apr 2019 L1 AGPL-3.0 No Details →
3.4.1 26 Mar 2019 L1 AGPL-3.0 No Details →
3.4.0 11 Mar 2019 L1 AGPL-3.0 No Details →
3.3.1 19 Feb 2019 L1 AGPL-3.0 No Details →
3.3.0 18 Feb 2019 L1 AGPL-3.0 No Details →
3.2.9 17 Jan 2019 L1 AGPL-3.0 No Details →
3.2.8 11 Jan 2019 L1 AGPL-3.0 No Details →
3.2.7 09 Jan 2019 L1 AGPL-3.0 No Details →
3.2.6 09 Jan 2019 L1 AGPL-3.0 No Details →
3.2.5 09 Jan 2019 L1 AGPL-3.0 No Details →
3.2.4 19 Dec 2018 L1 AGPL-3.0 No Details →
3.2.3 10 Dec 2018 L1 AGPL-3.0 No Details →
3.2.2 05 Oct 2018 L1 AGPL-3.0 No Details →
3.2.1 03 Oct 2018 L1 AGPL-3.0 No Details →
3.2.0 03 Oct 2018 L1 AGPL-3.0 No Details →
3.1.3 20 Sep 2018 L1 AGPL-3.0 No Details →
3.1.2 10 Sep 2018 L1 AGPL-3.0 No Details →
3.1.1 10 Sep 2018 L1 AGPL-3.0 No Details →
3.1.0 10 Sep 2018 L1 AGPL-3.0 No Details →
3.0.4 23 Aug 2018 L1 AGPL-3.0 No Details →
3.0.3 26 Jul 2018 L1 AGPL-3.0 No Details →
3.0.2 24 Jul 2018 L1 AGPL-3.0 No Details →
3.0.1 24 Jul 2018 L1 AGPL-3.0 No Details →
3.0.0 04 Jul 2018 L1 AGPL-3.0 No Details →
2.10.4 17 May 2018 L1 AGPL-3.0 No Details →
2.10.3 27 Apr 2018 L1 AGPL-3.0 No Details →
2.10.2 29 Mar 2018 L1 AGPL-3.0 No Details →
2.10.1 20 Feb 2018 L1 AGPL-3.0 No Details →
2.10.0 19 Feb 2018 L1 AGPL-3.0 No Details →
2.9.3 23 Jan 2018 L1 AGPL-3.0 No Details →
2.9.2 22 Jan 2018 L1 AGPL-3.0 No Details →
2.9.2-next 21 Dec 2017 L1 AGPL-3.0 No Details →
2.9.1 14 Dec 2017 L1 AGPL-3.0 No Details →
2.9.0 14 Dec 2017 L1 AGPL-3.0 No Details →
2.8.0-next 13 Dec 2017 L1 AGPL-3.0 No Details →
2.8.0 23 Nov 2017 L1 AGPL-3.0 No Details →
2.7.2 18 Oct 2017 L1 AGPL-3.0 No Details →
2.7.1 22 Sep 2017 L1 AGPL-3.0 No Details →
2.7.0 15 Sep 2017 L1 AGPL-3.0 No Details →
2.6.1 20 Jul 2017 L1 AGPL-3.0 No Details →
2.6.0 20 Jul 2017 L1 AGPL-3.0 No Details →
2.5.0 09 Jun 2017 L1 AGPL-3.0 No Details →
2.5.0-beta1 07 Jun 2017 L1 AGPL-3.0 No Details →
2.4.6 26 Apr 2017 L1 — No Details →
2.4.5 16 Apr 2017 L1 — No Details →
2.4.4 05 Apr 2017 L1 — No Details →
2.4.3 30 Mar 2017 L1 — No Details →
2.4.3-rc1 30 Mar 2017 L1 — No Details →
2.4.2 01 Mar 2017 L1 — No Details →
2.4.1 27 Feb 2017 L1 — No Details →
2.4.1-beta5 27 Feb 2017 L1 — No Details →
2.4.1-beta4 24 Feb 2017 L1 — No Details →
2.4.1-beta3 23 Feb 2017 L1 — No Details →
2.4.1-beta2 22 Feb 2017 L1 — No Details →
2.4.1-beta1 21 Feb 2017 L1 — No Details →
2.4.0 06 Feb 2017 L1 — No Details →
2.4.0-beta5 03 Feb 2017 L1 — No Details →
2.4.0-beta4 03 Feb 2017 L1 — No Details →
2.4.0-beta3 03 Feb 2017 L1 — No Details →
2.4.0-beta2 03 Feb 2017 L1 — No Details →
2.4.0-beta1 03 Feb 2017 L1 — No Details →
2.3.1-next 28 Jan 2017 L1 — No Details →
2.3.0 22 Jan 2017 L1 — No Details →

The newest 120 of 296 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 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 pm2

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-5891: pm2 Regular Expression Denial of Service Vulnerability 4.3 low No fix published 09 Jun 2025

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 pm2

Is pm2 safe to use?

Vulert records 1 vulnerabilities for pm2 in npm: 0 critical, 0 high, 0 medium and 1 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is pm2's Vulert package health score?

Vulert scores pm2 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of pm2 affected?

Yes. 7.1.0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does pm2 have?

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

How often are new pm2 vulnerabilities disclosed?

0 vulnerabilities were recorded for pm2 in the last 12 months, and the oldest entry in this database dates to 09 Jun 2025. 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 pm2 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 pm2 for upcoming vulnerabilities?

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