GHSA-mrgp-mrhc-5jrq
CRITICALGHSA-mrgp-mrhc-5jrq is a critical-severity (CVSS 10) CWE-913 vulnerability in vm2. 4 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-mrgp-mrhc-5jrq is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
vm2 vulnerable to Sandbox Escape resulting in Remote Code Execution on host
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
vm2npmDescription
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.11 of vm2
Workarounds
None.
References
Github Issue - https://github.com/patriksimek/vm2/issues/467 The file that was patched - https://github.com/patriksimek/vm2/blob/master/lib/setup-sandbox.js#L71 The commit with the patch - https://github.com/patriksimek/vm2/commit/d9a7f3cc995d3d861e1380eafb886cb3c5e2b873#diff-b1a515a627d820118e76d0e323fe2f0589ed50a1eacb490f6c3278fe3698f164
For more information
If you have any questions or comments about this advisory:
- Open an issue in VM2
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | vm2 | all versions | 3.9.11 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vm2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update vm2 to 3.9.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mrgp-mrhc-5jrq is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-mrgp-mrhc-5jrq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-mrgp-mrhc-5jrq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-mrgp-mrhc-5jrq in your dependencies?
O3 detects GHSA-mrgp-mrhc-5jrq across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.