Secuno
ENNL
Book demo

CVE-2026-92951

9.9 CRITICAL
  1. Published17 Sept 2026

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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-917278.1
Incorrect reference resolution in Extensions in Google Chrome on on Mac prior to…
CVE-2026-876188.3
Incorrect reference resolution in Storage in Google Chrome on on Windows prior to…
CVE-2026-876139.0
Incorrect reference resolution in Extensions in Google Chrome prior to 153.0.8010.36…
CVE-2026-875479.6
Incorrect reference resolution in FileSystem in Google Chrome prior to 153.0.8010.36…
CVE-2026-789859.6
Incorrect reference resolution in FileSystem in Google Chrome prior to 152.0.7977.65…
CVE-2026-676029.1
phpIPAM before 1.8.2 contains an authentication bypass vulnerability in the REST API…

Frequently asked

Is CVE-2026-92951 being actively exploited?

CVE-2026-92951 is not in the CISA KEV catalog.

How severe is CVE-2026-92951?

CVE-2026-92951 has a CVSS 3.1 base score of 9.9, rated critical.

How do I fix CVE-2026-92951?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-92951 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.