CVE-2026-92942 patriksimek CVE debrief

Who should care

Defenders responsible for systems using vm2, particularly those with untrusted or semi-trusted input, should assess exposure and potential impact. They should verify vm2 version and evaluate potential impact on systems using affected vm2 versions. Defenders should also consider upgrading to vm2 version 3.11.7 or later.

Why it matters

CVE-2026-92942 allows sandboxed code to block the host event loop, potentially leading to denial of service. Defenders should verify exposure, assess impact, and consider upgrading to vm2 version 3.11.7 or later.

• Denial of service via event loop blocking
• Potential for unbounded resource consumption
• Requires verification of affected versions and exploitation scenarios

Technical summary

vm2 before 3.11.7 does not enforce timeouts on code executed outside synchronous VM#run() calls. Sandboxed code can register FinalizationRegistry cleanup callbacks and block the host event loop when invoked by the V8 garbage collector. This issue can lead to denial of service. Defenders should verify exposure and assess potential impact. The CVE description and source references indicate that vm2 versions before 3.11.7 are affected. Specific version details and exploitation scenarios require verification. Defenders should prioritize verifying exposure and assessing potential impact, focusing on systems using vm2 versions before 3.11.7.

Defensive priority

Defenders should prioritize verifying exposure and assessing potential impact, focusing on systems using vm2 versions before 3.11.7.

Recommended defensive actions

• Verify vm2 version and assess exposure
• Evaluate potential impact on systems using affected vm2 versions
• Consider upgrading to vm2 version 3.11.7 or later
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE description and source references indicate that vm2 versions before 3.11.7 are affected, but specific version details and exploitation scenarios require verification. Defenders should verify exposure and assess potential impact. The issue allows sandboxed code to register FinalizationRegistry cleanup callbacks and block the host event loop when invoked by the V8 garbage collector.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.