Is vm2 3.12 vulnerable?

npm · 3 releases from 3.12.0 to 3.12.2 · latest vm2 is 3.12.2 · checked 2 Nov 2026

No known advisories in the last release

vm2 3.12.2, the last 3.12 release, has no known advisories. 4 advisories affect earlier 3.12.x releases, so update to 3.12.2.

Update within 3.12:npm install vm2@3.12.2

Is your project affected?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Fixed within 3.12.x, affecting earlier releases

  • CriticalCVE-2026-93605GHSA-pq68-rvw4-xp4r7 Oct 2026

    vm2 contains a sandbox escape vulnerability

    Affected
    <3.12.1
    Fixed in
    3.12.1
  • CriticalCVE-2026-100721GHSA-5h3f-q97h-ccvc5 Oct 2026

    vm2: NodeVM custom resolution bypasses external path boundaries

    Affected
    <3.12.2
    Fixed in
    3.12.2
  • HighCVE-2026-100722GHSA-2v2p-6j97-cjg95 Oct 2026

    vm2: Host Promise rejection from an exposed constructor can terminate the vm2 host process

    Affected
    <3.12.2
    Fixed in
    3.12.2
  • MediumCVE-2026-100723GHSA-489w-w794-jq945 Oct 2026

    vm2: NodeVM zlib Buffers expose pooled host memory across the VM boundary

    Affected
    <3.12.2
    Fixed in
    3.12.2

Which of your client projects are still on vm2 3.12?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact vm2 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

Other vm2 versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.