CVE-2026-24781
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 version 3.11.0, VM2 suffers from a sandbox breakout vulnerability through the inspect function. This allows attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system. This issue has been patched in version 3.11.0.
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 prior to 3.11.0 contain a sandbox breakout vulnerability in the inspect function that allows attackers to escape the VM2 sandbox isolation and execute arbitrary commands on the host system.
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
- 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.
-
Verify vm2 is installed in your projectRun 'npm list vm2' in your project directory or inspect your package.json file for vm2 in the dependencies, devDependencies, or peerDependencies sectionsAffected if vm2 appears in your dependencies or npm list output
-
Identify the installed vm2 versionRun 'npm list vm2' to see the installed version, or inspect node_modules/vm2/package.json for the 'version' fieldAffected if The displayed version is below 3.11.0 (for example, 3.10.x, 3.9.x, or any version lower than 3.11.0)
-
Confirm the inspect module is in useSearch your codebase for usage of vm2's inspect function, such as 'new Inspector', 'vm2.inspect', or any custom wrapper that utilizes vm2's inspection capabilitiesAffected if Your code directly invokes the inspect/Inspector functionality from vm2 for sandboxed code execution
You are affected if vm2 is installed in your environment and the installed version is lower than 3.11.0, especially if your application uses vm2's inspect functionality.
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 sandbox escape vulnerability.
vm2 version 3.11.0
- Identify all projects and dependencies that use the vm2 library
- Update vm2 dependency to version 3.11.0 or later (e.g., npm install vm2@^3.11.0 or yarn add vm2@^3.11.0)
- Run npm update or yarn upgrade to install the fixed version
- Verify the installed version is 3.11.0 or higher (npm list vm2)
- Rebuild and redeploy any applications using vm2
- Test that sandboxed code still functions correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24781 — 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-24781 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