CVE-2026-24118
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. 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 before version 3.11.0 contains a sandbox breakout vulnerability that allows attackers to escape the VM2 sandbox and execute arbitrary commands on the host system with the same privileges as the Node.js process.
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.
-
Check installed vm2 versionRun 'npm list vm2' in your project directory, or inspect your package.json file for the vm2 version entry under dependenciesAffected if The reported version is lower than 3.11.0
-
Locate vm2 installation pathRun 'npm root -g' or check local node_modules folder, then verify the version in node_modules/vm2/package.jsonAffected if The version in node_modules/vm2/package.json shows a version below 3.11.0
-
Identify vm2 sandbox usage in codeSearch your codebase for 'require("vm2")' or 'import * as vm2' to find where vm2 is being usedAffected if Your application imports and uses vm2 to run untrusted code
-
Determine if sandbox accepts external inputReview the code paths where vm2 is invoked and check if user-supplied data is passed to the sandbox runner (VM, Node, or Function)Affected if User-controlled data flows directly into vm2 without sanitization
You are affected if vm2 version is below 3.11.0 and your application passes untrusted input to 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. After upgrading, verify that the sandbox isolation still functions correctly and conduct penetration testing to confirm the breakout is no longer possible.
vm2 version 3.11.0
- 1. Identify all dependencies that require vm2 in your project by checking package.json files
- 2. Run 'npm list vm2' or 'yarn list vm2' to identify the current installed version
- 3. Update vm2 to version 3.11.0 or later using 'npm update vm2' or 'yarn upgrade vm2'
- 4. If vm2 is a transitive dependency, update the direct dependency that depends on it to a version that includes the fixed vm2
- 5. Run 'npm list vm2' again to confirm the updated version is installed
- 6. Test that your application functions correctly with the updated vm2 version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24118 — 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-24118 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