CVE-2026-119188

validatingZero is analyzing and reversing it now.

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
24mrunning
differential validationcurrent stage
timeline
0 = trigger signal
trigger signal +0dcve.org publication+2.6dvalidating
0
+1d
+2d
+3d

description

Forge versions before 1.4.1 can mishandle an interrupted fragmented TLS handshake when using forge.tls.createConnection(). A remote TLS peer may cause an uncaught exception, disrupting the affected connection or the process hosting it. Exposure requires an application to use the affected TLS connection implementation.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade forge to version 1.4.1 or later. Until upgraded, reduce exposure by limiting untrusted remote peers' access to services using forge.tls.createConnection().

fixed in 1.4.1

check
building now
exploit
not yet
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
24m
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

Run in progress: no artifact yet.

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": "in_pipeline",
  "anchor_state": "anchored",
  "title": "TLS record processing denial of service in forge",
  "summary": "Forge versions before 1.4.1 can mishandle an interrupted fragmented TLS handshake when using forge.tls.createConnection(). A remote TLS peer may cause an uncaught exception, disrupting the affected connection or the process hosting it. Exposure requires an application to use the affected TLS connection implementation.",
  "mitigation": "Upgrade forge to version 1.4.1 or later. Until upgraded, reduce exposure by limiting untrusted remote peers' access to services using forge.tls.createConnection().",
  "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": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.8878325,
  "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-29 23: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.