CVE-2026-92951

validatedZero produced an exploit or a check.

GHSA-6fvh-fgmg-3x7v ↗EUVD-2026-81600 ↗

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).kevAttacks confirmed in the real world.
npm:vm2 <= 3.11.6
fixed in 3.11.7
ETK-2026-255, permanent identifier
pkg:npm/vm2
+14dTTV
17mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0dcheck available+14dagent stopped
0
+5d
+10d
+15d

description

vm2 before 3.11.7 can let sandboxed NodeVM code evade an external-package allowlist by requesting a similarly named package. This can cause unauthorized package code to run in the host process when the application uses a custom resolver and that resolver can find a colliding package in an attacker-influenced location.

mitigation

Upgrade the npm vm2 package to version 3.11.7 or later. Until upgraded, do not use custom resolvers that search attacker-writable package locations, and restrict such resolver paths to trusted dependencies.

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.54%44th percentile
agent run time
17m
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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-255",
  "cve_id": "CVE-2026-92951",
  "display_id": "CVE-2026-92951",
  "ghsa_id": "GHSA-6fvh-fgmg-3x7v",
  "euvd_id": "EUVD-2026-81600",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper package allowlist matching in vm2 NodeVM",
  "summary": "vm2 before 3.11.7 can let sandboxed NodeVM code evade an external-package allowlist by requesting a similarly named package. This can cause unauthorized package code to run in the host process when the application uses a custom resolver and that resolver can find a colliding package in an attacker-influenced location.",
  "mitigation": "Upgrade the npm vm2 package to version 3.11.7 or later. Until upgraded, do not use custom resolvers that search attacker-writable package locations, and restrict such resolver paths to trusted dependencies.",
  "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": 9.9,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": 0.0054,
  "epss_percentile": 0.4428,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 16.869106833333333,
  "t0_at": "2026-09-17T13:46:10.792000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-01T16:43:43.917408+00:00",
      "days": 14.123300062592593,
      "is_lower_bound": false,
      "measured_at": "2026-09-17T13:46:10.792000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-09-17T13:46:10.792000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-17T13:46:10.792000+00:00",
      "url": "https://github.com/advisories/GHSA-c48m-32m9-vx93"
    }
  }
}

published 2026-10-01 16:26Z
last change 2026-10-21 05:31Z

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.