CVE-2026-92941

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

GHSA-98xx-8mx4-x7cm ↗EUVD-2026-81591 ↗

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.3, <= 3.11.6
fixed in 3.11.7
ETK-2026-251, permanent identifier
pkg:npm/vm2
19d 20h 57msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+338h32m
0
+2h
+4h
+6h
+8h
+10h

description

vm2 before 3.11.7 can let untrusted NodeVM code alter the host process's default TLS certificate authorities. An attacker must be able to execute sandboxed code with the tls and url built-ins enabled; subsequent host TLS clients may then trust attacker-controlled certificates or experience connection failures.

mitigation

Upgrade vm2 to version 3.11.7. Until upgrading, do not allow the tls or url built-ins in NodeVM instances that execute untrusted code.

fixed in 3.11.7

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.29%20th 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-92941

{
  "etk_id": "ETK-2026-251",
  "cve_id": "CVE-2026-92941",
  "display_id": "CVE-2026-92941",
  "ghsa_id": "GHSA-98xx-8mx4-x7cm",
  "euvd_id": "EUVD-2026-81591",
  "status": "published",
  "anchor_state": "anchored",
  "title": "TLS trust-store sandbox escape in vm2",
  "summary": "vm2 before 3.11.7 can let untrusted NodeVM code alter the host process's default TLS certificate authorities. An attacker must be able to execute sandboxed code with the tls and url built-ins enabled; subsequent host TLS clients may then trust attacker-controlled certificates or experience connection failures.",
  "mitigation": "Upgrade vm2 to version 3.11.7. Until upgrading, do not allow the tls or url built-ins in NodeVM instances that execute untrusted code.",
  "vendor": "npm",
  "product": "npm:vm2",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.11.3, <= 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:L",
  "epss_score": 0.0029,
  "epss_percentile": 0.2019,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 15.376113983333333,
  "t0_at": "2026-09-17T13:46:04.885000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-17T13:46:04.885000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-17T13:46:04.885000+00:00",
      "url": "https://github.com/advisories/GHSA-98xx-8mx4-x7cm"
    }
  }
}

published 2026-10-01 16:02Z
last change 2026-10-21 11:38Z

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.