Skip to main content
VulnerabilityPublished

CVE-2026-47683: patriksimek vm2 · Unthrottled Resource Allocation

Affects patriksimek vm2Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 3.11.6 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.11.6
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

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, where the bufferAllocLimit enforcement covers all relevant Buffer allocation methods and prevents bypass. No other mitigation is indicated or necessary as the issue is fixed in this version.

Description

CVE-2026-47683 is a high-severity vulnerability in the open source Node.js sandbox vm2 prior to version 3.11.6. It involves insufficient enforcement of buffer allocation limits, allowing sandboxed code to bypass configured caps on memory allocation. This can lead to large synchronous external-memory allocations that may exhaust the host process. The issue is fixed in vm2 version 3.11.6.

References

Community reviews

Loading reviews…