CVE-2026-92953

waiting for further signalsZero needs more public information before it can validate it.

GHSA-3vgf-8m4q-q4qr ↗EUVD-2026-81602 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
npm:vm2 >= 3.11.0, <= 3.11.7
fixed in 3.11.8
ETK-2026-691, permanent identifier
pkg:npm/vm2
15d 09h 18msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+441h51m
0
+2h
+4h
+6h
+8h
+10h

description

vm2 versions before 3.11.8 do not fully isolate host typed-array and ArrayBuffer prototypes from code running in a default VM sandbox. An attacker able to execute JavaScript in that sandbox can modify shared host prototype behavior, affecting subsequently created host typed arrays and ArrayBuffers.

mitigation

Upgrade vm2 to version 3.11.8 or later. Until upgraded, do not run untrusted JavaScript in vm2 VM sandboxes.

fixed in 3.11.8

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.50%41st percentile
agent run time
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-17 13:46Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-09-17 13:46Z
    ghsa: trigger signal, started the run
  2. 2026-09-17 13:46Z

this entry in the feed

GET /api/v1/feed/CVE-2026-92953

{
  "etk_id": "ETK-2026-691",
  "cve_id": "CVE-2026-92953",
  "display_id": "CVE-2026-92953",
  "ghsa_id": "GHSA-3vgf-8m4q-q4qr",
  "euvd_id": "EUVD-2026-81602",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Host prototype pollution in vm2 VM sandboxes",
  "summary": "vm2 versions before 3.11.8 do not fully isolate host typed-array and ArrayBuffer prototypes from code running in a default VM sandbox. An attacker able to execute JavaScript in that sandbox can modify shared host prototype behavior, affecting subsequently created host typed arrays and ArrayBuffers.",
  "mitigation": "Upgrade vm2 to version 3.11.8 or later. Until upgraded, do not run untrusted JavaScript in vm2 VM sandboxes.",
  "vendor": "npm",
  "product": "npm:vm2",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.11.0, <= 3.11.7"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "3.11.8"
      ],
      "package_name": "vm2",
      "purl": "pkg:npm/vm2"
    }
  ],
  "cwes": null,
  "cvss_score": 10,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H",
  "epss_score": 0.005,
  "epss_percentile": 0.4169,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 15.002897283333333,
  "t0_at": "2026-09-17T13:46:12.146000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-17T13:46:12.146000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-17T13:46:12.146000+00:00",
      "url": "https://github.com/advisories/GHSA-3vgf-8m4q-q4qr"
    }
  }
}

published 2026-10-05 23:22Z
last change 2026-10-21 08:40Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.