Node node forge: Prior to 1.4.1, the affected implementation used forge.tls.createConnection(), TLS record processing
Affects node-node-forgeSource GCVE Database
Not known to be exploited · CVSS 7.5 High · fixed in 1.4.1 : patch node-node-forge soon.
Data as of 5 Nov 2026, 12:35 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.5 |
|---|
- Patch
- Available – fixed in 1.4.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 22.04 LTSnode-node-forgepkg:deb/ubuntu/node-node-forge?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 20.04 LTSnode-node-forgepkg:deb/ubuntu/node-node-forge?arch=source&distro=focalOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used forge.tls.createConnection(), TLS record processing, process() to process the relevant input or security decision. node-forge processed received TLS records recursively, consuming one JavaScript stack frame per record in a single input chunk. A remote peer could send thousands of small records together and exhaust the call stack, causing an uncaught exception and denial of service. This issue is fixed in version 1.4.1.
References
- ubuntu.com/security/CVE-2026-119187 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-119187 (opens in a new tab)
- github.com/digitalbazaar/forge/commit/817e2ce0d0f6d8a25bc9c2670615c38a9ffdc51c (opens in a new tab)
- github.com/digitalbazaar/forge/releases/tag/v1.4.1 (opens in a new tab)
- github.com/digitalbazaar/forge/security/advisories/GHSA-hqq3-7jhf-c5jx (opens in a new tab)