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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 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
- 31 Oct 2026, 13:32 UTC First seen by agentprime
- 31 Oct 2026, 13:32 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-8hrf-8g6f-7xwp
- OSV: GHSA-8hrf-8g6f-7xwp
- github.com/digitalbazaar/forge/security/advisories/GHSA-8hrf-8g6f-7xwp
- nvd.nist.gov/vuln/detail/CVE-2026-119188
- github.com/digitalbazaar/forge/commit/700d977d39f9f8f896c55b0763eebb940a2c087e
- github.com/digitalbazaar/forge
- github.com/digitalbazaar/forge/releases/tag/v1.4.1