CVE-2026-24781: vm2: Sandbox Breakout Through Inspect
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 68.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: patriksimek vm2 3.11.0.
Low priority for now. Upgrade to patriksimek vm2 3.11.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
vm2 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.
- Published
- May 4, 2026
- Updated
- Oct 26, 2026
- EPSS
- 1.1% · 68th percentile
- CWE
- CWE-94
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| vm2 project | vm2 | cpe:2.3:a:vm2_project:vm2 |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
patriksimek vm2
- < 3.11.0affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- vm2 project vm2before 3.11.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | vm2 | before 3.11.0 | 3.11.0 |
Same product
vm2 project: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-30547Sandbox Escape in vm262This week
- CVE-2023-29017vm2 Sandbox Escape vulnerability58Plan
- CVE-2022-36067vm2 vulnerable to Sandbox Escape before v3.9.1154Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-24118May 4, 2026 · VM2 Sandbox Breakout Through __lookupGetter__39Monitor
- ← EarlierCVE-2026-24120May 4, 2026 · vm2: Sandbox Breakout Through Promise Species39Monitor
- Later →CVE-2026-26332May 4, 2026 · vm2 is an open source vm/sandbox for Node.js.40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| patriksimek vm2 | 3.11.0 · description | Vendor (CNA) |
| npm:vm2 | 3.11.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-263320 days apartvm2 is an open source vm/sandbox for Node.js.40Plan
- CVE-2026-439979 days apartvm2 is an open source vm/sandbox for Node.js.40Plan
- CVE-2026-440059 days apartvm2 is an open source vm/sandbox for Node.js.40Plan
- CVE-2026-440069 days apartvm2 is an open source vm/sandbox for Node.js.40Plan
- CVE-2026-2270998 days apartvm2 has a Sandbox Escape40Plan
- CVE-2026-241180 days apartVM2 Sandbox Breakout Through __lookupGetter__39Monitor
Not on record for this CVE: EPSS history · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- github.com/patriksimek/vm2/commit/bdd3d15e57bc4ec5e70365cd79f7cb0256e5f88c
- github.com/patriksimek/vm2/commit/fd266d084e0a3322d0f71ba2a8dc4c96cd030228
- github.com/patriksimek/vm2/releases/tag/v3.11.0
- access.redhat.com/errata/RHSA-2026:26234
- access.redhat.com/errata/RHSA-2026:36754
- access.redhat.com/security/cve/CVE-2026-24781
- bugzilla.redhat.com/show_bug.cgi?id=2466531
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-24781.json
Vendor advisories and official records. Exploit/PoC links are deliberately left out.