CVE-2026-100722

validatedZero produced an exploit or a check.

GHSA-2v2p-6j97-cjg9 ↗EUVD-2026-87857 ↗

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).+8.9dkevAttacks confirmed in the real world.
npm:vm2 <= 3.12.1
fixed in 3.12.2
ETK-2026-709, permanent identifier
pkg:npm/vm2
+9.0dTTV
18mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0dpublic poc+8.9dcheck available+9.0dagent stopped
0
+2d
+4d
+6d
+8d
+10d

description

vm2 versions before 3.12.2 can leave rejected native Promises unhandled when they are returned through an exposed host constructor. An attacker able to execute untrusted code in a VM can terminate the Node.js host process if the application exposes such a constructor and uses strict unhandled-rejection behavior.

mitigation

Upgrade the npm vm2 package to version 3.12.2 or later. Until upgraded, do not expose constructable host APIs that may return rejected native Promises to untrusted VM code.

fixed in 3.12.2

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.
0.26%16th percentile
agent run time
18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-27 01:28Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+8.9d
Δ 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-27 01:28Z
    ghsa: trigger signal, started the run
  2. 2026-09-27 01:28Z
    public poc, published 2026-10-05 23:19Z
  3. 2026-09-27 01:28Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-709",
  "cve_id": "CVE-2026-100722",
  "display_id": "CVE-2026-100722",
  "ghsa_id": "GHSA-2v2p-6j97-cjg9",
  "euvd_id": "EUVD-2026-87857",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unhandled Promise rejection process termination in vm2",
  "summary": "vm2 versions before 3.12.2 can leave rejected native Promises unhandled when they are returned through an exposed host constructor. An attacker able to execute untrusted code in a VM can terminate the Node.js host process if the application exposes such a constructor and uses strict unhandled-rejection behavior.",
  "mitigation": "Upgrade the npm vm2 package to version 3.12.2 or later. Until upgraded, do not expose constructable host APIs that may return rejected native Promises to untrusted VM code.",
  "vendor": "npm",
  "product": "npm:vm2",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 3.12.1"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "3.12.2"
      ],
      "package_name": "vm2",
      "purl": "pkg:npm/vm2"
    }
  ],
  "cwes": null,
  "cvss_score": 8.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H",
  "epss_score": 0.0026,
  "epss_percentile": 0.1665,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 18.21561345,
  "t0_at": "2026-09-27T01:28:29.295000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-06T01:59:37.592940+00:00",
      "days": 9.02162381875,
      "is_lower_bound": false,
      "measured_at": "2026-09-27T01:28:29.295000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-10-05T23:19:55+00:00",
      "days": 8.91071417824074,
      "is_lower_bound": false,
      "measured_at": "2026-09-27T01:28:29.295000+00:00",
      "url": "https://github.com/advisories/GHSA-2v2p-6j97-cjg9"
    },
    "trigger_signal": {
      "at": "2026-09-27T01:28:29.295000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-27T01:28:29.295000+00:00",
      "url": "https://github.com/advisories/GHSA-2v2p-6j97-cjg9"
    }
  }
}

published 2026-10-06 01:41Z
last change 2026-10-21 09:43Z

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.