CVE-2026-92937

validatedZero produced an exploit or a check.

GHSA-3f84-vwv5-r42g ↗EUVD-2026-81587 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+14dkevAttacks confirmed in the real world.
npm:vm2 = 3.11.6
fixed in 3.11.7
ETK-2026-253, permanent identifier
pkg:npm/vm2
+14dTTV
13mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0dpublic poc+14dcheck availableagent stopped
0
+5d
+10d
+15d

description

vm2 can allow untrusted JavaScript to escape its sandbox and run code in the host Node.js process. Exploitation requires an application to expose a host-realm Promise to sandboxed code and for that Promise to reject with an error containing a reference to a host object.

mitigation

Upgrade vm2 to version 3.11.7. Until the upgrade is complete, do not run untrusted code with vm2 where sandboxed code can access host Promises or host-object references through rejected errors.

fixed in 3.11.7

check
available
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.
contextual
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.
1.0%63rd percentile
agent run time
13m
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).
+14d
Δ to kevAttacks confirmed in the real world.
–

outcome

Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.

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
    public poc, published 2026-10-01 15:32Z
  3. 2026-09-17 13:46Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-253",
  "cve_id": "CVE-2026-92937",
  "display_id": "CVE-2026-92937",
  "ghsa_id": "GHSA-3f84-vwv5-r42g",
  "euvd_id": "EUVD-2026-81587",
  "status": "published",
  "anchor_state": "anchored",
  "title": "vm2 sandbox escape through rejected host Promises",
  "summary": "vm2 can allow untrusted JavaScript to escape its sandbox and run code in the host Node.js process. Exploitation requires an application to expose a host-realm Promise to sandboxed code and for that Promise to reject with an error containing a reference to a host object.",
  "mitigation": "Upgrade vm2 to version 3.11.7. Until the upgrade is complete, do not run untrusted code with vm2 where sandboxed code can access host Promises or host-object references through rejected errors.",
  "vendor": "npm",
  "product": "npm:vm2",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "= 3.11.6"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "3.11.7"
      ],
      "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:H/I:H/A:H",
  "epss_score": 0.0103,
  "epss_percentile": 0.633,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 12.86150765,
  "t0_at": "2026-09-17T13:46:02.195000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-01T16:30:05.258484+00:00",
      "days": 14.11392434587963,
      "is_lower_bound": false,
      "measured_at": "2026-09-17T13:46:02.195000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-10-01T15:32:10+00:00",
      "days": 14.073701446759259,
      "is_lower_bound": false,
      "measured_at": "2026-09-17T13:46:02.195000+00:00",
      "url": "https://github.com/advisories/GHSA-647f-g98j-qq25"
    },
    "trigger_signal": {
      "at": "2026-09-17T13:46:02.195000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-17T13:46:02.195000+00:00",
      "url": "https://github.com/advisories/GHSA-647f-g98j-qq25"
    }
  }
}

published 2026-10-01 16:17Z
last change 2026-10-21 13:12Z

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.