vm2: timeout Option Bypass via FinalizationRegistry Cleanup Callback (Unbounded Host Event-Loop Block)

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.0049, the 42nd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

1. 31 Oct 2026, 13:34 UTC First seen by agentprime
2. 31 Oct 2026, 13:34 UTC Confirmed by OSV

Sources

• GitHub Advisory Database: GHSA-r4fx-v8hh-22mv
• OSV: GHSA-r4fx-v8hh-22mv
• github.com/patriksimek/vm2/security/advisories/GHSA-r4fx-v8hh-22mv
• nvd.nist.gov/vuln/detail/CVE-2026-92942
• github.com/patriksimek/vm2/commit/fe2fcca2a1e693548993eccc624489dc4cb586b4
• github.com/patriksimek/vm2
• github.com/patriksimek/vm2/releases/tag/v3.11.7
• www.vulncheck.com/advisories/vm2-before-3.11.7-timeout-bypass-via-finalizationregistry

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.