vm2 Sandbox Escape vulnerability
Published 15 May 2023 · Updated 10 Sept 2026
Affected package
- Affected
- <3.9.18
- Fixed in
- 3.9.18
npm install vm2@3.9.18Details
A sandbox escape vulnerability exists in vm2 for versions up to 3.9.17. It abuses an unexpected creation of a host object based on the specification of Proxy.
Impact
A threat actor can bypass the sandbox protections to gain remote code execution rights on the host running the sandbox.
Patches
This vulnerability was patched in the release of version 3.9.18 of vm2.
Workarounds
None.
References
PoC - https://gist.github.com/arkark/e9f5cf5782dec8321095be3e52acf5ac
For more information
If you have any questions or comments about this advisory:
- Open an issue in VM2
Thanks to @arkark (Takeshi Kaneko) of GMO Cybersecurity by Ierae, Inc. for disclosing this vulnerability.
Is GHSA-whpj-8f3w-67p5 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected vm2, and gives you the command that fixes it.
References
- Linkgithub.com/patriksimek/vm2/security/advisories/GHSA-whpj-8f3w-67p5
- Advisorynvd.nist.gov/vuln/detail/CVE-2023-32314
- Linkgithub.com/patriksimek/vm2/commit/d88105f99752305c5b8a77b63ddee3ec86912daf
- Linkgist.github.com/arkark/e9f5cf5782dec8321095be3e52acf5ac
- Packagegithub.com/patriksimek/vm2
- Linkgithub.com/patriksimek/vm2/releases/tag/3.9.18
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.