Vulnerability Database · npm · vm2 · Version
vm2 3.12.2
3.12.2 is affected by 28 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 3.12.2.
Critical 20 High 4 Medium 3 Low 1 Unrated 0
-
Released 08 Sep 2026
Status latest release
Licence MIT
Also known from other sources 0
Newer releases 83
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
vm2 3.12.2 vulnerabilities
28 vulnerabilities cover vm2 3.12.2. Scroll the table for all of them, or open the full list in the database.
Looking for another version, or everything Vulert holds for vm2?
Questions
About vm2 3.12.2
Is vm2 3.12.2 vulnerable?
Yes. 28 vulnerabilities in the Vulert database cover vm2 3.12.2: 20 critical, 4 high, 3 medium and 1 low. The upgrade Vulert recommends is 3.12.2, and each entry above names the fixed version to move to.
Which version of vm2 should I use instead of 3.12.2?
3.12.2 is the version Vulert recommends for this release line, which is also the release the publisher currently ships. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 3.12.2 the latest release of vm2?
Yes. 3.12.2 is the current release, published 08 Sep 2026. Staying on the current line is what keeps you inside the publisher's fixes.
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.