CVE-2026-44008
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedvm2 is an open source vm/sandbox for Node.js. Prior to 3.11.2, the new method neutralizeArraySpeciesBatch works with objects from the other side but can call into this side via getter on the array prototype exposing objects of the wrong side into the sandbox. This can be used to get host objects and get the host Function object. This allows attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system. This vulnerability is fixed in 3.11.2.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencevm2 sandbox escape vulnerability in neutralizeArraySpeciesBatch method that improperly exposes host-side objects to the sandbox via array prototype getters, allowing attackers to access the host Function object and execute arbitrary code outside the sandbox.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.11.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Find installed vm2 versionRun 'npm list vm2' in your project directory, or inspect your package.json dependencies for the vm2 entryAffected if The version listed is less than 3.11.2 (e.g., 3.11.1, 3.11.0, or any version starting with 3.10.x or lower)
-
Check if vm2 sandbox processes untrusted inputReview your application code where vm2 is imported and used; look for instances where VM.run, VMContext, or similar vm2 APIs execute code from user-controlled sources such as HTTP request bodies, user-uploaded files, or database fieldsAffected if Untrusted or externally-sourced code is passed to any vm2 sandbox API (VM.run, new VM, etc.)
-
Verify neutralizeArraySpeciesBatch is reachableThis is an internal method invoked during array operations within the sandbox. If your sandboxed code performs array manipulations (Array.isArray, array methods that trigger species constructor access), the vulnerable code path is exercisedAffected if Your sandboxed code performs array operations that could trigger the array species getter, which is common in many JavaScript workloads
You are affected if vm2 version is below 3.11.2 AND your application runs untrusted code within the vm2 sandbox.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.11.2
Upgrade vm2 to version 3.11.2 or later. If immediate upgrade is not feasible, avoid running untrusted code in vm2 until the patch can be applied.
3.11.2
- 1. Identify all applications and services that depend on the vm2 package
- 2. Check the current installed version of vm2 in each project using 'npm list vm2' or 'yarn list vm2'
- 3. For each affected project, update vm2 to version 3.11.2 or later by running 'npm install [email protected]' or 'yarn add [email protected]'
- 4. Verify the upgrade was successful by running 'npm list vm2' or 'yarn list vm2' to confirm version 3.11.2 or higher is installed
- 5. Test your application thoroughly to ensure the sandbox functionality works as expected after the upgrade
- 6. Redeploy all affected applications with the updated dependency
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44008 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-44008 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data