Skip to main content
VulnerabilityPublished Updated

CVE-2026-47698: patriksimek vm2 · Improper Control of Dynamically-Managed Code Resources

Affects patriksimek vm2Source CVE Database V5

0
Compare

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

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 62% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.11.6
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 17 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 15 Nov 2026.

What to do

Upgrade patriksimek vm2 to 3.11.6.

Affected software

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

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

AI-suggested

Upgrade vm2 to version 3.11.6 or later to apply the official fix that addresses this vulnerability. No other mitigation is required as the issue is resolved in this version.

Description

CVE-2026-47698 is a critical vulnerability in the open source Node.js sandbox vm2 prior to version 3.11.6. The flaw allows sandboxed code to bypass prototype chain protections via stacked indirection through Function.prototype.call, enabling arbitrary host command execution. This is due to improper control of dynamically-managed code resources in specific vm2 modules. The issue is fixed in vm2 version 3.11.6.

References

Community reviews

Loading reviews…