CVE-2026-44006
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.0, It is possible to reach BaseHandler.getPrototypeOf, which can be used to get arbitrary prototypes. 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 before 3.11.0 contain a prototype pollution vulnerability where the BaseHandler.getPrototypeOf trap can be reached, allowing attackers to access arbitrary object prototypes. This bypasses sandbox isolation and can lead to code execution or information disclosure.
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.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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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.
-
Identify vm2 installationRun 'npm list vm2' in your project directory, or inspect package.json and package-lock.json for the vm2 dependencyAffected if vm2 version is listed as less than 3.11.0 or no version is specified and the package is present
-
Verify vm2 is actively importedSearch your codebase for require('vm2') or import statements referencing vm2 in your JavaScript/TypeScript filesAffected if vm2 is imported or required in your application's source code
-
Check for sandbox execution of external inputReview code paths where vm2 sandbox is used to execute code that originates from user input, external APIs, or untrusted sourcesAffected if The sandbox runs code from untrusted or external sources
-
Confirm getPrototypeOf or similar reflective methods are accessibleInspect the vm2 usage patterns in your code to see if object reflection or prototype manipulation operations are performed within the sandbox contextAffected if Code executed within the vm2 sandbox can access or manipulate object prototypes
You are affected if vm2 version is below 3.11.0 AND your application uses vm2 to run untrusted or external code within the 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 patch the prototype pollution vulnerability.
vm2 version 3.11.0 or later
- Identify all projects that depend on the vm2 package using npm ls vm2 or equivalent dependency scanning tools
- Update the vm2 dependency in package.json to version 3.11.0 or later (e.g., "vm2": "^3.11.0")
- Run npm update vm2 or npm install to fetch the fixed version
- Reinstall all dependencies with npm install to ensure lockfile consistency
- Rebuild and redeploy any applications or services that depend on vm2
- Verify the installed version with npm list vm2 to confirm the upgrade was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44006 — 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-44006 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