CVE-2026-119188

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

GHSA-8hrf-8g6f-7xwp ↗EUVD-2026-113365 ↗

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.
digitalbazaar forge <= 1.4.0
fixed in 1.4.1
CWE-248 Uncaught Exception
ETK-2026-3004Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:npm/node-forge
53msince last run
31mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal −2.6dcve.org publicationwaiting for further signals+0.2d
−2d
−1d
0

description

node-forge versions before 1.4.1 are affected when using its TLS connection implementation. An unauthenticated peer that can reach a TLS endpoint, or a server contacted by a TLS client, can trigger an uncaught exception that may terminate the hosting Node.js process during handshake processing.

mitigation

Upgrade the npm node-forge package to version 1.4.1 or later. Until upgrading, wrap calls to the TLS connection processing method in exception handling and close the affected socket on error.

fixed in 1.4.1

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.
–
agent run time
31m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-29 19:21Z
Δ 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-10-27 05:02Z
  2. 2026-10-29 19:21Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3004",
  "cve_id": "CVE-2026-119188",
  "display_id": "CVE-2026-119188",
  "ghsa_id": "GHSA-8hrf-8g6f-7xwp",
  "euvd_id": "EUVD-2026-113365",
  "status": "published",
  "anchor_state": "anchored",
  "title": "TLS handshake denial of service in node-forge",
  "summary": "node-forge versions before 1.4.1 are affected when using its TLS connection implementation. An unauthenticated peer that can reach a TLS endpoint, or a server contacted by a TLS client, can trigger an uncaught exception that may terminate the hosting Node.js process during handshake processing.",
  "mitigation": "Upgrade the npm node-forge package to version 1.4.1 or later. Until upgrading, wrap calls to the TLS connection processing method in exception handling and close the affected socket on error.",
  "vendor": "digitalbazaar",
  "product": "forge",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 1.4.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "1.4.1"
      ],
      "package_name": "node-forge",
      "purl": "pkg:npm/node-forge"
    }
  ],
  "cwes": [
    248
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 30.50664075,
  "t0_at": "2026-10-29T19:21:27.347000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-27T05:02:48+00:00",
      "days": -2.596288738425926,
      "is_lower_bound": false,
      "measured_at": "2026-10-29T19:21:27.347000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-119188"
    }
  }
}

published 2026-10-29 19:52Z
last change 2026-10-30 00:09Z

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.