Host event-loop hang via FinalizationRegistry timeout bypass
Published Sep 17, 2026 · Updated Sep 18, 2026
Uncontrolled resource consumption in Patrik Simek vm2 3.11.6 and earlier allows remote attackers to hang the host Node.js event loop. FinalizationRegistry cleanup callbacks run after VM#run() returns, beyond doWithTimeout(), so an unbounded callback bypasses configured timeout accounting. Reachability requires an application to execute attacker-controlled JavaScript in a timeout-configured VM; garbage collection triggers the host-process hang.
Summary
What happened
Uncontrolled resource consumption in Patrik Simek vm2 3.11.6 and earlier allows remote attackers to hang the host Node.js event loop. FinalizationRegistry cleanup callbacks run after VM#run() returns, beyond doWithTimeout(), so an unbounded callback bypasses configured timeout accounting. Reachability requires an application to execute attacker-controlled JavaScript in a timeout-configured VM; garbage collection triggers the host-process hang.
The record
- CVE
- CVE-2026-92942
- Published
- Sep 17, 2026
- Updated
- Sep 18, 2026
- Vendor
- Patrik Simek
- Product
- vm2
- Classifications
- CWE-841, CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.11.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- FinalizationRegistry timeout-bypass proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started