{"items":[{"id":"NVI-00013251","kind":"vulnerability","title":"vm2: timeout Option Bypass via FinalizationRegistry Cleanup Callback (Unbounded Host Event-Loop Block)","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-r4fx-v8hh-22mv","CVE-2026-92942"],"plain_summary":"GitHub lists this reviewed advisory for vm2. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-34c7b54e8f2a1773c200f8ee6300f2af"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-05T22:35:04.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-a5fd7912ecc1eeb5e86ad2bc3b98e088"},{"kind":"CVSS","as_of":"2026-09-18T20:17:30.843Z","value":"7.5 HIGH (3.1)","meaning":"disclosure@vulncheck.com severity; no combined Null risk score.","source_id":"sr-3a5e1e2f9a06cfc63fe795832f788afa"},{"kind":"CVSS","as_of":"2026-09-18T20:17:30.843Z","value":"8.7 HIGH (4.0)","meaning":"disclosure@vulncheck.com severity; no combined Null risk score.","source_id":"sr-3a5e1e2f9a06cfc63fe795832f788afa"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.488%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.42018. Missing scores are unknown.","source_id":"sr-34c7b54e8f2a1773c200f8ee6300f2af"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-a5fd7912ecc1eeb5e86ad2bc3b98e088","url":"https://github.com/advisories/GHSA-r4fx-v8hh-22mv","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-r4fx-v8hh-22mv","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T01:39:10.636Z"},{"id":"sr-3a5e1e2f9a06cfc63fe795832f788afa","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92942","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-92942","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-04T09:59:50.242Z"},{"id":"sr-34c7b54e8f2a1773c200f8ee6300f2af","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-92942","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:29:11.296Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-a5fd7912ecc1eeb5e86ad2bc3b98e088"],"technology":"vm2","known_exclusions":[],"conditions_summary":"### Vulnerability Summary\n \nvm2's `VM({ timeout })` option is documented and relied upon as the mechanism that bounds how long sandboxed code may execute. In the current implementation, the timeout only wraps the single synchronous call to `VM#run()` (via `doWithTimeout` → `this._runScript(script)` in `lib/vm.js`). It does not, and structurally cannot, bound code that the V8 engine itself schedules to run *after* that call has already returned.\n \n`FinalizationRegistry` and `WeakRef` are exposed to sandboxed code completely unmodified — they are not present anywhere in `lib/setup-sandbox.js`'s list of specially-wrapped/hardened globals (only `WeakMap`, `Promise`, `Proxy`, `Reflect`, etc. receive hardening there). Sandboxed code can register a `FinalizationRegistry` callback against an object it creates and immediately drops. `VM#run()` returns normally, well within the configured timeout, because registration is instant. At some later point — determined entirely by the V8 garbage collector, and forceable on demand by the host process (e.g. under memory pressure, or via `--expose-gc`) — the engine invokes the sandboxed cleanup callback directly. This invocation is **not** mediated by","public_affected_ranges":["<= 3.11.6"]}],"null_published_at":"2026-11-07T18:43:15.097Z","source_updated_at":"2026-10-05T22:35:04.000Z","source_disclosed_at":"2026-10-05T22:35:04.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-01T01:39:10.636Z"},{"id":"NVI-00013251","kind":"vulnerability","title":"vm2: timeout Option Bypass via FinalizationRegistry Cleanup Callback (Unbounded Host Event-Loop Block)","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-r4fx-v8hh-22mv","CVE-2026-92942"],"plain_summary":"GitHub lists this reviewed advisory for vm2. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-3a5e1e2f9a06cfc63fe795832f788afa"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-05T22:35:04.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-a5fd7912ecc1eeb5e86ad2bc3b98e088"},{"kind":"CVSS","as_of":"2026-09-18T20:17:30.843Z","value":"7.5 HIGH (3.1)","meaning":"disclosure@vulncheck.com severity; no combined Null risk score.","source_id":"sr-3a5e1e2f9a06cfc63fe795832f788afa"},{"kind":"CVSS","as_of":"2026-09-18T20:17:30.843Z","value":"8.7 HIGH (4.0)","meaning":"disclosure@vulncheck.com severity; no combined Null risk score.","source_id":"sr-3a5e1e2f9a06cfc63fe795832f788afa"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-a5fd7912ecc1eeb5e86ad2bc3b98e088","url":"https://github.com/advisories/GHSA-r4fx-v8hh-22mv","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-r4fx-v8hh-22mv","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T01:39:10.636Z"},{"id":"sr-3a5e1e2f9a06cfc63fe795832f788afa","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92942","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-92942","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-04T09:59:50.242Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-a5fd7912ecc1eeb5e86ad2bc3b98e088"],"technology":"vm2","known_exclusions":[],"conditions_summary":"### Vulnerability Summary\n \nvm2's `VM({ timeout })` option is documented and relied upon as the mechanism that bounds how long sandboxed code may execute. In the current implementation, the timeout only wraps the single synchronous call to `VM#run()` (via `doWithTimeout` → `this._runScript(script)` in `lib/vm.js`). It does not, and structurally cannot, bound code that the V8 engine itself schedules to run *after* that call has already returned.\n \n`FinalizationRegistry` and `WeakRef` are exposed to sandboxed code completely unmodified — they are not present anywhere in `lib/setup-sandbox.js`'s list of specially-wrapped/hardened globals (only `WeakMap`, `Promise`, `Proxy`, `Reflect`, etc. receive hardening there). Sandboxed code can register a `FinalizationRegistry` callback against an object it creates and immediately drops. `VM#run()` returns normally, well within the configured timeout, because registration is instant. At some later point — determined entirely by the V8 garbage collector, and forceable on demand by the host process (e.g. under memory pressure, or via `--expose-gc`) — the engine invokes the sandboxed cleanup callback directly. This invocation is **not** mediated by","public_affected_ranges":["<= 3.11.6"]}],"null_published_at":"2026-11-04T10:04:35.933Z","source_updated_at":"2026-10-05T22:35:04.000Z","source_disclosed_at":"2026-10-05T22:35:04.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-11-01T01:39:10.636Z"},{"id":"NVI-00013251","kind":"vulnerability","title":"vm2: timeout Option Bypass via FinalizationRegistry Cleanup Callback (Unbounded Host Event-Loop Block)","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-r4fx-v8hh-22mv","CVE-2026-92942"],"plain_summary":"GitHub lists this reviewed advisory for vm2. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-a5fd7912ecc1eeb5e86ad2bc3b98e088"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-05T22:35:04.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-a5fd7912ecc1eeb5e86ad2bc3b98e088"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-a5fd7912ecc1eeb5e86ad2bc3b98e088","url":"https://github.com/advisories/GHSA-r4fx-v8hh-22mv","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-r4fx-v8hh-22mv","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T01:39:10.636Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-a5fd7912ecc1eeb5e86ad2bc3b98e088"],"technology":"vm2","known_exclusions":[],"conditions_summary":"### Vulnerability Summary\n \nvm2's `VM({ timeout })` option is documented and relied upon as the mechanism that bounds how long sandboxed code may execute. In the current implementation, the timeout only wraps the single synchronous call to `VM#run()` (via `doWithTimeout` → `this._runScript(script)` in `lib/vm.js`). It does not, and structurally cannot, bound code that the V8 engine itself schedules to run *after* that call has already returned.\n \n`FinalizationRegistry` and `WeakRef` are exposed to sandboxed code completely unmodified — they are not present anywhere in `lib/setup-sandbox.js`'s list of specially-wrapped/hardened globals (only `WeakMap`, `Promise`, `Proxy`, `Reflect`, etc. receive hardening there). Sandboxed code can register a `FinalizationRegistry` callback against an object it creates and immediately drops. `VM#run()` returns normally, well within the configured timeout, because registration is instant. At some later point — determined entirely by the V8 garbage collector, and forceable on demand by the host process (e.g. under memory pressure, or via `--expose-gc`) — the engine invokes the sandboxed cleanup callback directly. This invocation is **not** mediated by","public_affected_ranges":["<= 3.11.6"]}],"null_published_at":"2026-11-01T07:29:12.932Z","source_updated_at":"2026-10-05T22:35:04.000Z","source_disclosed_at":"2026-10-05T22:35:04.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-01T01:39:10.636Z"}],"next_cursor":null,"snapshot_revision":"42594"}