Skip to main content
VulnerabilityPublished

CVE-2026-44000: patriksimek vm2 · Protection Mechanism Failure

Affects patriksimek vm2Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.11.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 May 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 30 Oct 2026.

What to do

Upgrade patriksimek vm2 to 3.11.0.

Affected software

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

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

AI-suggested

This vulnerability is fixed in vm2 version 3.11.0. Users should upgrade to version 3.11.0 or later to remediate this issue. Patch status is not explicitly stated beyond the fix in 3.11.0, so verifying the upgrade and consulting the official vm2 repository or vendor advisory for confirmation is recommended.

Description

CVE-2026-44000 is a vulnerability in the vm2 Node.js sandbox prior to version 3.11.0 that allows host object identity to leak into the sandbox via host Promise resolution. This occurs because the Promise fulfillment wrapper uses ensureThis() instead of a stronger cross-realm conversion, enabling sandbox code to directly interact with host objects, including identity checks and state mutation. The vulnerability is fixed in vm2 version 3.11.0. The CVSS 3.1 base score is 6.

References

Community reviews

Loading reviews…