CVE-2026-24120
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.10.5, the fix for CVE-2023-37466 is insufficient and can be circumvented allowing 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.10.5.
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.10.5 contain a sandbox escape vulnerability where the insufficient fix for CVE-2023-37466 can be bypassed, allowing attackers to escape the VM2 sandbox and execute arbitrary commands on the host system with critical severity.
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.10.5CVSS 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 if vm2 is installed in the projectRun 'npm list vm2' in the project directory, or inspect package.json dependencies for 'vm2', or check node_modules/vm2/package.jsonAffected if vm2 appears in installed dependencies
-
Determine the installed vm2 versionRead the version field from node_modules/vm2/package.json or from npm list vm2 outputAffected if The version is lower than 3.10.5 (e.g., 3.10.4, 3.10.0, any 3.x.x below 3.10.5)
-
Identify if the codebase creates VM contexts from vm2Search source code for patterns such as 'new VM()', 'new VMCustomInspector', 'vm2', or imports from 'vm2' that create sandbox instancesAffected if Code creates VM instances using vm2 for processing
-
Determine if untrusted input reaches the vm2 sandboxReview code flow to see whether user-supplied data, external API input, or dynamically evaluated code is passed to the VM context methods such as 'run()', 'execute()', or 'call()'Affected if Untrusted or user-controlled data is passed to vm2 VM methods for execution
The environment is affected if vm2 version is below 3.10.5 AND the code actively uses vm2 to run untrusted code in a sandboxed context.
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.10.5
Upgrade vm2 to version 3.10.5 or later to apply the complete patch. If immediate upgrade is not feasible, avoid processing untrusted code through vm2 until the patch can be applied.
3.10.5
- 1. Identify all projects and dependencies that use the vm2 library with versions prior to 3.10.5
- 2. Run a dependency audit (e.g., npm ls vm2, or grep for vm2 in package-lock.json) to find all instances
- 3. Update the vm2 dependency in package.json to version 3.10.5 or later: npm install [email protected] or npm install vm2@latest
- 4. Run npm update to refresh lockfiles
- 5. Rebuild and redeploy all affected applications
- 6. Test the application functionality to ensure the sandbox works correctly with the updated version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24120 — 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-24120 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