CVE-2026-119187

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

GHSA-hqq3-7jhf-c5jx ↗EUVD-2026-113364 ↗

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-674 Uncontrolled Recursion
ETK-2026-3003Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:npm/node-forge
3h 29msince last run
25mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dcve.org publication+2.6dwaiting for further signals
0
+1d
+2d

description

Forge versions before 1.4.1 are affected when handling inbound TLS records. A remote TLS peer can cause a denial of service by triggering excessive call-stack use; the service must accept TLS input from that peer.

mitigation

Upgrade the forge package to version 1.4.1 or later. Until upgraded, restrict access to TLS endpoints to trusted peers where feasible.

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.
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.
–
agent run time
25m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-29 19:19Z
Δ 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

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-27 05:01Z
  2. 2026-10-29 19:19Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3003",
  "cve_id": "CVE-2026-119187",
  "display_id": "CVE-2026-119187",
  "ghsa_id": "GHSA-hqq3-7jhf-c5jx",
  "euvd_id": "EUVD-2026-113364",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stack exhaustion denial of service in Forge TLS processing",
  "summary": "Forge versions before 1.4.1 are affected when handling inbound TLS records. A remote TLS peer can cause a denial of service by triggering excessive call-stack use; the service must accept TLS input from that peer.",
  "mitigation": "Upgrade the forge package to version 1.4.1 or later. Until upgraded, restrict access to TLS endpoints to trusted peers where feasible.",
  "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": [
    674
  ],
  "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": 24.78513591666667,
  "t0_at": "2026-10-29T19:19:36.824000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-27T05:01:46+00:00",
      "days": -2.59572712962963,
      "is_lower_bound": false,
      "measured_at": "2026-10-29T19:19:36.824000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-119187"
    }
  }
}

published 2026-10-29 19:42Z
last change 2026-10-29 23:03Z

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.