Skip to main content
VulnerabilityPublished

CVE-2026-92951: patriksimek vm2 · Use of Incorrectly-Resolved Name or Reference

Affects patriksimek vm2Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.4 Critical : upgrade to 3.11.7 as a priority.

Data as of 1 Nov 2026, 22:58 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 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 1 Nov 2026.

What to do

Upgrade patriksimek vm2 to 3.11.7.

Affected software

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

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

AI-suggested

A fix is available in vm2 version 3.11.7. Users should upgrade to version 3.11.7 or later to remediate this vulnerability. No alternative mitigations or temporary fixes are indicated in the provided data.

Description

vm2 before 3.11.7 contains an incorrect authorization vulnerability in the external package allowlist check that uses non-exact substring matching instead of full package-name boundary validation. Attackers can bypass the allowlist by requiring a colliding package name that contains an allowlisted package substring, causing vm2 to load and execute unauthorized host packages in the host context.

References

Community reviews

Loading reviews…