Secuno
ENNL
Book demo

CVE-2026-92934

9.0 CRITICAL
  1. Published17 Sept 2026

Description

vm2 before 3.11.8 contains an incomplete fix for Error.cause sanitization that allows sandbox escape when revisited host-wrapped AggregateError objects are caught within a single exception handler traversal. Attackers can exploit cycle detection bypass in handleException to access unsanitized host proxies embedded in the errors array, enabling full remote code execution and process information disclosure from the sandbox.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityHigh
Privileges requiredNone
User interactionNone
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:H/PR:N/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-9295610.0
vm2 versions 3.10.1 through 3.11.6 contain a sandbox escape reachable from a default…
CVE-2026-929489.9
vm2 versions >= 3.9.6 and <= 3.11.6 are affected by a NodeVM builtin allowlist bypass…
CVE-2026-929449.8
vm2 versions 3.10.2 through 3.11.6 contain a sandbox escape vulnerability on Node.js 26…
CVE-2026-929389.9
vm2 versions 3.11.3 through 3.11.6 expose Node.js's host node:sqlite module to code…
CVE-2026-203319.6
As part of Cisco's ongoing commitment to proactive security and product quality, the…
CVE-2026-768258.4
RestrictedPython is a tool that helps define a subset of the Python language for…

Frequently asked

Is CVE-2026-92934 being actively exploited?

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

How severe is CVE-2026-92934?

CVE-2026-92934 has a CVSS 3.1 base score of 9.0, rated critical.

How do I fix CVE-2026-92934?

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-92934 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.