Skip to main content
VulnerabilityPublished Updated

CVE-2026-22709: patriksimek vm2 · Code Injection

Affects patriksimek vm2Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 3.10.2 as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.2% chance of exploitation in 30 days – higher than 69% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.10.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade patriksimek vm2 to 3.10.2.

Affected software

ProductAffectedFixed in
patriksimekvm2Affected
  • <3.10.2
Fixed in
  • 3.10.2
npmvm2pkg:npm/vm2Other threatsAffected
  • <3.10.2
Fixed in
  • 3.10.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade vm2 to version 3.10.2 or later, where the vulnerability is patched. For environments where immediate upgrading is not feasible, consider disabling or restricting the use of vm2 sandboxes, especially in contexts processing untrusted code. Implement strict code review and validation processes for any code executed within vm2. Employ runtime monitoring and anomaly detection to identify suspicious behavior indicative of sandbox escape attempts. Additionally, isolate systems running vm2 sandboxes using network segmentation and least privilege principles to limit potential damage. Regularly audit dependencies and maintain an up-to-date inventory of Node.js packages to quickly identify vulnerable versions. Finally, educate developers and security teams about the risks associated with sandbox bypass vulnerabilities and the importance of timely patching.

Description

vm2 is an open source vm/sandbox for Node.js. In vm2 prior to version 3.10.2, `Promise.prototype.then` `Promise.prototype.catch` callback sanitization can be bypassed. This allows attackers to escape the sandbox and run arbitrary code. In lib/setup-sandbox.js, the callback function of `localPromise.prototype.then` is sanitized, but `globalPromise.prototype.then` is not sanitized. The return value of async functions is `globalPromise` object. Version 3.10.2 fixes the issue.

References

Community reviews

Loading reviews…