VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

vm2: vulnerability history, versions and safety

vm2 is a package in the npm ecosystem. Vulert records 108 vulnerabilities for it across 83 releases, from Oct 2021 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
108 vulnerabilities recorded C71 H19 M16 L2
i
28 with no fix published

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

See the unfixed vulnerabilities →
i
96 in the last 12 months

Most recent disclosure 07 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all vm2 vulnerabilities

Vulert verdict on vm2 3.12.2 i

Updated on 23 Oct 2026

Careful: 3.12.2 has 28 known vulnerabilities, and 28 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Unfixed 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 3.12.2 — affected i
  • Vulnerabilities on record 108 over 4 years · 96 in the last year i
  • Latest disclosure 07 Oct 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 28 i
  • Depended on by 4,328 packages i
  • Stars 4,109 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month 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 vm2, 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
3.12.2 08 Sep 2026 C20 H4 M3 L1 MIT No Details →
3.12.1 03 Sep 2026 C22 H6 M5 L1 MIT No Details →
3.12.0 01 Sep 2026 C24 H6 M5 L1 MIT No Details →
3.11.8 27 Aug 2026 C24 H6 M5 L1 MIT No Details →
3.11.7 24 Aug 2026 C28 H7 M6 L1 MIT No Details →
3.11.6 14 Aug 2026 C2 MIT No Details →
3.11.5 18 May 2026 C43 H12 M10 L1 MIT No Details →
3.11.4 18 May 2026 C43 H12 M10 L1 MIT No Details →
3.11.3 11 May 2026 C46 H14 M10 L2 MIT No Details →
3.11.2 03 May 2026 C39 H14 M10 L2 MIT No Details →
3.11.1 01 May 2026 C41 H14 M11 L2 MIT No Details →
3.11.0 01 May 2026 C42 H14 M11 L2 MIT No Details →
3.10.5 17 Feb 2026 C1 H1 MIT Yes Details →
3.10.4 04 Feb 2026 C1 MIT Yes Details →
3.10.3 25 Jan 2026 C47 H16 M12 L2 MIT No Details →
3.10.2 17 Jan 2026 C47 H16 M12 L2 MIT No Details →
3.10.1 09 Jan 2026 C46 H16 M12 L2 MIT No Details →
3.10.0 24 Oct 2025 C44 H16 M12 L2 MIT No Details →
3.9.19 16 May 2023 C42 H16 M12 L2 MIT No Details →
3.9.18 15 May 2023 C42 H16 M12 L2 MIT No Details →
3.9.17 17 Apr 2023 C43 H16 M13 L2 MIT No Details →
3.9.16 11 Apr 2023 C44 H16 M13 L2 MIT No Details →
3.9.15 06 Apr 2023 C45 H16 M13 L2 MIT No Details →
3.9.14 05 Feb 2023 C46 H16 M13 L2 MIT No Details →
3.9.13 08 Dec 2022 C46 H16 M13 L2 MIT No Details →
3.9.12 29 Nov 2022 C46 H16 M13 L2 MIT No Details →
3.9.11 28 Aug 2022 C46 H16 M13 L2 MIT No Details →
3.9.10 05 Jul 2022 C47 H16 M13 L2 MIT No Details →
3.9.9 24 Feb 2022 C48 H16 M13 L2 MIT No Details →
3.9.8 16 Feb 2022 C48 H16 M13 L2 MIT No Details →
3.9.7 10 Feb 2022 C48 H16 M13 L2 MIT No Details →
3.9.6 08 Feb 2022 C48 H16 M13 L2 MIT No Details →
3.9.5 17 Oct 2021 C46 H16 M11 L2 MIT No Details →
3.9.4 12 Oct 2021 C46 H16 M11 L2 MIT No Details →
3.9.3 05 Apr 2021 C47 H16 M11 L2 MIT No Details →
3.9.2 29 Apr 2020 C47 H16 M11 L2 MIT No Details →
3.9.1 29 Mar 2020 C47 H16 M11 L2 MIT No Details →
3.9.0 21 Mar 2020 C47 H16 M11 L2 MIT No Details →
3.8.4 13 Sep 2019 C47 H16 M11 L2 MIT No Details →
3.8.3 31 Jul 2019 C47 H16 M11 L2 MIT No Details →
3.8.2 12 Jun 2019 C47 H16 M11 L2 MIT No Details →
3.8.1 02 May 2019 C47 H16 M11 L2 MIT No Details →
3.8.0 21 Apr 2019 C47 H16 M11 L2 MIT No Details →
3.7.0 15 Apr 2019 C47 H16 M11 L2 MIT No Details →
3.6.11 07 Apr 2019 C47 H16 M11 L2 MIT No Details →
3.6.10 28 Jan 2019 C47 H17 M11 L2 MIT No Details →
3.6.9 26 Jan 2019 C47 H17 M11 L2 MIT No Details →
3.6.8 26 Jan 2019 C47 H17 M11 L2 MIT No Details →
3.6.7 26 Jan 2019 C47 H17 M11 L2 MIT No Details →
3.6.6 02 Jan 2019 C47 H17 M11 L2 MIT No Details →
3.6.5 31 Dec 2018 C47 H17 M11 L2 MIT No Details →
3.6.4 17 Oct 2018 C47 H17 M11 L2 MIT No Details →
3.6.3 06 Aug 2018 C47 H17 M11 L2 MIT No Details →
3.6.2 05 Jul 2018 C47 H17 M11 L2 MIT No Details →
3.6.1 27 Jun 2018 C47 H17 M11 L2 MIT No Details →
3.6.0 11 May 2018 C47 H17 M11 L2 MIT No Details →
3.5.2 04 Oct 2017 C47 H17 M11 L2 MIT No Details →
3.5.1 03 Oct 2017 C47 H17 M11 L2 MIT No Details →
3.5.0 31 Aug 2017 C47 H17 M11 L2 MIT No Details →
3.4.6 30 Mar 2017 C47 H17 M11 L2 MIT No Details →
3.4.5 30 Mar 2017 C47 H17 M11 L2 MIT No Details →
3.4.4 30 Mar 2017 C47 H17 M11 L2 MIT No Details →
3.4.3 29 Mar 2017 C47 H17 M11 L2 MIT No Details →
3.4.2 29 Mar 2017 C47 H17 M11 L2 MIT No Details →
3.4.1 28 Mar 2017 C47 H17 M11 L2 MIT No Details →
3.4.0 28 Mar 2017 C47 H17 M11 L2 MIT No Details →
3.3.1 27 Mar 2017 C47 H17 M11 L2 MIT No Details →
3.3.0 27 Mar 2017 C47 H17 M11 L2 MIT No Details →
3.2.0 10 Feb 2017 C47 H17 M11 L2 MIT No Details →
3.1.0 03 Sep 2016 C47 H17 M11 L2 MIT No Details →
3.0.1 20 Jul 2016 C47 H17 M11 L2 MIT No Details →
3.0.0 20 Jun 2016 C47 H17 M11 L2 MIT No Details →
2.0.2 06 Apr 2016 C47 H17 M11 L2 MIT No Details →
2.0.0 16 Mar 2016 C47 H17 M11 L2 MIT No Details →
1.0.1 22 Dec 2015 C47 H17 M11 L2 MIT No Details →
1.0.0 17 Dec 2015 C47 H17 M11 L2 MIT No Details →
0.2.4 11 Dec 2015 C47 H17 M11 L2 MIT No Details →
0.2.3 20 Sep 2015 C47 H17 M11 L2 MIT No Details →
0.2.2 12 Feb 2015 C47 H17 M11 L2 MIT No Details →
0.2.1 20 Dec 2014 C47 H17 M11 L2 MIT No Details →
0.2.0 11 Oct 2014 C47 H17 M11 L2 MIT No Details →
0.1.1 14 Jan 2014 C47 H17 M11 L2 MIT No Details →
0.1.0 14 Jan 2014 C47 H17 M11 L2 MIT No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 4
  • 2023 7
  • 2026 96

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

03 Vulnerabilities

Recorded vulnerabilities for vm2

The 5 most severe of 108 vulnerabilities recorded for this package

Search all 108 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Critical Remote Code Execution Vulnerability in vm2 Package 10.0 critical No fix published 17 Sep 2026
CVE-2026-92937: vm2 Critical RCE Vulnerability via Promise Rejection Bypass 10.0 critical 3.11.7 01 Oct 2026
CVE-2026-93605: vm2 Sandbox Escape Vulnerability Allows Host Command Execution 10.0 critical 3.12.1 07 Oct 2026
CVE-2022-36067: vm2 Sandbox Escape Remote Code Execution 10.0 critical 3.9.11 28 Sep 2022
CVE-2026-92941: vm2 NodeVM Vulnerability Allows Host Process TLS Trust Store Manipulation 10.0 critical 3.11.7 01 Oct 2026

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 vm2

Is vm2 safe to use?

Vulert records 108 vulnerabilities for vm2 in npm: 71 critical, 19 high, 16 medium and 2 low. 28 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is vm2's Vulert package health score?

Vulert scores vm2 50/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 vm2 affected?

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

Which version of vm2 should I use?

3.12.2 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 vm2 have?

108 vulnerabilities are recorded for vm2 in the npm ecosystem: 71 critical, 19 high, 16 medium and 2 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new vm2 vulnerabilities disclosed?

96 vulnerabilities were recorded for vm2 in the last 12 months, and the oldest entry in this database dates to 19 Oct 2021. 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 vm2 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 vm2 for upcoming vulnerabilities?

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