CVE-2026-44005
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. From 3.9.6 to 3.10.5, vm2's bridge exposes mutable proxies for real host-realm intrinsic prototypes and then forwards sandbox writes into the underlying host objects with otherReflectSet() and otherReflectDefineProperty(), which lets attacker-controlled JavaScript running in a default VM or inherited NodeVM mutate shared host Object.prototype, Array.prototype, and Function.prototype from inside the sandbox This vulnerability is fixed in 3.11.0.
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 versions 3.9.6 through 3.10.5 contain a sandbox escape vulnerability where the bridge exposes mutable proxies for host-realm intrinsic prototypes, allowing attacker-controlled JavaScript running inside the sandbox to mutate the host's Object.prototype, Array.prototype, and Function.prototype via otherReflectSet() and otherReflectDefineProperty(). This enables full prototype pollution on the host from within the isolated VM.
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.9.6, < 3.11.0CVSS 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
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/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.
-
Locate vm2 in project dependenciesSearch for vm2 in package.json under dependencies or devDependencies, or check node_modules/vm2/package.jsonAffected if vm2 is listed as a direct or transitive dependency
-
Determine installed vm2 versionRun 'npm list vm2' or 'npm list' to see the installed version, or read the version field from node_modules/vm2/package.jsonAffected if The installed version is 3.9.6, 3.9.7, 3.9.8, 3.9.9, 3.9.10, 3.10.0, 3.10.1, 3.10.2, 3.10.3, 3.10.4, or 3.10.5 (or any version >= 3.9.6 and < 3.11.0)
-
Identify sandbox usage with untrusted codeSearch source code for vm2 imports and vm.run() or new VM() calls that execute untrusted JavaScript inputAffected if The application runs untrusted JavaScript code inside vm2 using vm.run(), new VM(), or similar execution methods
You are affected if vm2 version is 3.9.6 or higher but below 3.11.0 and your application executes untrusted JavaScript 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.0
Upgrade vm2 to version 3.11.0 or later to remediate this vulnerability. Review any custom sandbox configurations that may have additional exposure vectors.
vm2 version 3.11.0 or later
- Check the current version of vm2 in your project by examining package.json or package-lock.json
- Upgrade vm2 to version 3.11.0 or later by running: npm install vm2@^3.11.0 or yarn add vm2@^3.11.0
- Run npm install or yarn to update the dependency and regenerate lock files
- Test the application to ensure the sandbox functionality works correctly after the upgrade
- Verify that the upgraded version is now 3.11.0 or later by running npm list vm2
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing6.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 $3,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44005 — 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-44005 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