ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-119188

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

Published Oct 30, 2026 · catalog updated Oct 30, 2026 · Forge: Denial of service

Last checked Nov 6, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-119188. EPSS is 0.41%. Act only if a listed version of Forge: Denial of service is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Forge: Denial of service).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.41%
Remediation
Version ranges on file
Affected products
npm node-forge

### Summary A connection created with throws an uncaught from when it receives a record of another content type while waiting for the rest of a handshake message that was split across records. A peer can trigger this with 18 bytes before the handshake, without authentication, which terminates Node.js processes that use the documented socket wiring. Fixed in node-forge 1.4.1. ### Details In , handles a record that arrives while a handshake message split across records is incomplete. If the record has any other content type (change_cipher_spec, alert, application_data or heartbeat), forge correctly reports "Invalid fragmented record." through with a fatal alert. That fatal error closes and resets the connection, which sets to . then continues with and throws out of . The code is unchanged since the first release. RFC 5246 section 6.2.1 allows a handshake message to be fragmented across records, and RFC 8446 section 5.1 forbids interleaving handshake messages with other record types. Failing the connection with is the intended behavior; the bug is the crash after the error. node-forge reports TLS protocol errors through the callback, so applications do not normally wrap in / . When is called from a Node.js socket handler, as in the documented usage, the exception is uncaught and terminates the process. The fix returns from right after the fatal error. The connection is failed, the alert is sent and the callback is called as before, and no longer throws. ### Patches Fixed in node-forge 1.4.1. The connection still fails with a fatal alert and the callback, but no longer throws. ### Workarounds Wrap every call to in / . The connection has already been failed and closed when the exception is thrown, so the exception can be ignored or the socket destroyed. ### Proof of concept Input (server mode), two records, 18 bytes: 16 03 01 00 06 01 00 00 10 03 01 handshake record: ClientHello header announcing 16 bytes, 2 present 15 03 01 00 02 02 28 alert record // c = forge.tls.crea

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm node-forge0 → 1.4.1
  • npm node-forge<= 1.4.0

How to fix CVE-2026-119188

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-119188. EPSS is 0.41%. Act only if a listed version of Forge: Denial of service is installed.

Which versions are affected?

Compare what you have installed with 0 → 1.4.1, <= 1.4.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-248; CWE-476: NULL Pointer Dereference. EPSS 0.41%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 30, 2026 · GitHub Advisory Database

    Detected

    ### Summary A connection created with throws an uncaught from when it receives a record of another content type while waiting for the rest of a handshake message that was split across records. A peer can trigger this with 18 bytes before the handshake, without authentication, which terminates Node.js processes that use the documented socket wiring. Fixed in node-forge 1.4.1. ### Details In , handl

  2. Oct 30, 2026 · GitHub Advisory Database

    Fix available

    node-forge fixed in 1.4.1

  3. Oct 30, 2026 · GitHub Advisory Database

    Fix available

    node-forge fixed in 1.4.1

  4. Oct 30, 2026 · GitHub Advisory Database

    Updated

    ### Summary A connection created with throws an uncaught from when it receives a record of another content type while waiting for the rest of a handshake message that was split across records. A peer can trigger this with 18 bytes before the handshake, without authentication, which terminates Node.js processes that use the documented socket wiring. Fixed in node-forge 1.4.1. ### Details In , handl

Sources

  • CVE.orgVulnerability recordCVE-2026-119188

    Official CVE identifier

    cve.org
  • GitHub Advisory DatabasePackage advisoryGHSA-8hrf-8g6f-7xwp

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

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-119188

    A connection created with forge.tls.createConnection() throws an uncaught TypeError from process() when it receives a record of another content type while waiting for the rest of a handshake message that was split across records. A peer can trigger this with 18 bytes before the handshake, without authentication, which terminates Node.js processes that use the documented socket wiring. Fixed in nod

    advisories.gitlab.com
  • OpenSSF OSV / OSV ScannerPackage advisoryGHSA-8hrf-8g6f-7xwp

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

    osv.dev

References

Freshness

Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • GitHub Advisory DatabaseNov 6, 2026
  • GitLab Advisory DatabaseNov 3, 2026
  • CVE.orgOct 31, 2026
  • OpenSSF OSV / OSV ScannerOct 31, 2026