Skip to content
Fencer Vulns
critical 10.0

CVE-2022-36067 in the critical feed json

vm2 vulnerable to Sandbox Escape before v3.9.11

published 2022-09-06 4 y ago modified 2026-06-17 4 mo ago also GHSA-mrgp-mrhc-5jrq , EUVD-2022-6880

cvss
10.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
47.9%
EPSS 47.9% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

vm2 is a sandbox that can run untrusted code with whitelisted Node's built-in modules. In versions prior to version 3.9.11, a threat actor can bypass the sandbox protections to gain remote code execution rights on the host running the sandbox. This vulnerability was patched in the release of version 3.9.11 of vm2. There are no known workarounds.

Patch / fix

  • npm vm2 3.9.11
  • vm2_project vm2 3.9.11

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-36067 updated cvss 8.8

vm2: Sandbox Escape in vm2

  • Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/console-rhel8
    affected: workaround, no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
total
Assessed
18 mo ago

Exploit prediction

47.87% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/patriksimek/vm2/blob/master/lib/setup-sandbox.js#L71 referenced PoC, tagged "exploit" by a source, unverified
  • oxeye.io https://www.oxeye.io/blog/vm2-sandbreak-vulnerability-cve-2022-36067 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm vm2
<3.9.11
3.9.11

Affected products

  • patriksimek vm2

Classification

Weakness
  • CWE-913 Improper Control of Dynamically-Managed Code Resources

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.