ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-119187

Forge: Denial of service in TLS record processing via call stack exhaustion

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-119187. 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 Connections created with processed received TLS records recursively, one stack level per record. A peer can send one chunk of thousands of small records, such as heartbeat records, which are accepted before the handshake, and throws , which terminates Node.js processes that use the documented socket wiring. Fixed in node-forge 1.4.1. ### Details In , reads one record and passes it to , which calls the handler for the record type from . Every handler ( , , for fragmented messages, and the other handshake handlers) ends by calling again to continue with the next buffered record, or the next message in the same record. Each record therefore adds → → handler to the call stack. In Node.js 24, about 2,300 eight-byte records (under 20 KB) in one chunk are enough for to throw . maps heartbeat records to in every client and server state, so heartbeat records are processed before the handshake without any extension negotiation. The attack needs no authentication and no valid handshake messages. Both server connections (attacked by a client) and client connections (attacked by the server they connect to) are affected. Other record types recurse the same way: a handshake message fragmented over many records, many HelloRequest messages in one record, or many application data records after the handshake. 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. If the exception is caught, the connection is left partially processed and should be discarded. No specification is violated; this is an implementation flaw (uncontrolled recursion). The fix makes iterative. The record-reading code moves into , and runs it in a loop. A handler's call to without new data, made while records are being processed, now only flags that the loop should continue. Calls with new data are processed right away as bef

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-119187

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-119187. 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-674. 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 Connections created with processed received TLS records recursively, one stack level per record. A peer can send one chunk of thousands of small records, such as heartbeat records, which are accepted before the handshake, and throws , which terminates Node.js processes that use the documented socket wiring. Fixed in node-forge 1.4.1. ### Details In , reads one record and passes it to ,

  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 Connections created with processed received TLS records recursively, one stack level per record. A peer can send one chunk of thousands of small records, such as heartbeat records, which are accepted before the handshake, and throws , which terminates Node.js processes that use the documented socket wiring. Fixed in node-forge 1.4.1. ### Details In , reads one record and passes it to ,

Sources

  • CVE.orgVulnerability recordCVE-2026-119187

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-119187

    30-day exploitation probability 0.41%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-hqq3-7jhf-c5jx

    Forge: Denial of service in TLS record processing via call stack exhaustion

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

    Connections created with forge.tls.createConnection() processed received TLS records recursively, one stack level per record. A peer can send one chunk of thousands of small records, such as heartbeat records, which are accepted before the handshake, and process() throws RangeError: Maximum call stack size exceeded, which terminates Node.js processes that use the documented socket wiring. Fixed in

    advisories.gitlab.com
  • OpenSSF OSV / OSV ScannerPackage advisoryGHSA-hqq3-7jhf-c5jx

    Forge: Denial of service in TLS record processing via call stack exhaustion

    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.

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