Advisory record · GHSA-8hrf-8g6f-7xwp

Forge: Denial of service in TLS record processing via a record interleaved with a fragmented handshake message

CVSS 7.5 HighEPSS 0.0041 · 35th percentile

Published by the GitHub Advisory Database at 30 Oct 2026, 23:02 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
node-forgenpm<1.4.11.4.1
Identifiers
GHSA-8hrf-8g6f-7xwp · CVE-2026-119188
Weakness (CWE)
CWE-248 · CWE-476
Published
30 Oct 2026
Updated
30 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Affected: node-forge versions before 1.4.1, specifically the TLS implementation created by forge.tls.createConnection(). A peer that can reach a forge TLS endpoint, without authentication, can send 18 bytes during the handshake, a fragmented handshake record followed by a record of another content type, which makes process() throw an uncaught TypeError. In Node.js applications that call process() from a socket data handler, as the documented usage does, this terminates the process. Upgrade to node-forge 1.4.1, which returns cleanly after the fatal unexpected_message alert.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0041, the 35th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:32 UTC First seen by agentprime
  2. 31 Oct 2026, 13:32 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.