Is CVE-2026-119188 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-119188 being exploited in the wild.

How severe is CVE-2026-119188?

High severity, with a CVSS score of 7.5, published 29 October 2026.

Which products and versions are affected?

Digital Bazaar Forge prior to 1.4.1; node-forge (npm) <= 1.4.0, SEMVER:introduced=0,fixed=1.4.1.

Is there a fix for CVE-2026-119188?

Yes. node-forge (npm): upgrade to 1.4.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-119188 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-119188?

Check whether you run Digital Bazaar Forge or node-forge (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-119188: Forge TLS handshake denial of service

Q: Is there a fix for CVE-2026-119188?

Yes. node-forge (npm): upgrade to 1.4.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-119188 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-119188?

Check whether you run Digital Bazaar Forge or node-forge (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-119188 · Severity: high · CVSS 7.5 · Published 2026-10-29

Forge is a JavaScript library that implements TLS (Transport Layer Security), the encryption protocol used to secure web traffic and other network communications. A flaw in how it processes fragmented TLS handshake messages could allow a remote attacker to crash the connection or the entire hosting process by sending specially crafted records, causing a denial of service.

Technologies: Digital Bazaar Forge, node-forge (npm). Vendors: Digital Bazaar, npm.

Quick answers

Is CVE-2026-119188 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-119188 being exploited in the wild.
How severe is CVE-2026-119188?: High severity, with a CVSS score of 7.5, published 29 October 2026.
Which products and versions are affected?: Digital Bazaar Forge prior to 1.4.1; node-forge (npm) <= 1.4.0, SEMVER:introduced=0,fixed=1.4.1.
Is there a fix for CVE-2026-119188?: Yes. node-forge (npm): upgrade to 1.4.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-119188 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-119188?: Check whether you run Digital Bazaar Forge or node-forge (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

node-forge (npm): upgrade to 1.4.1 or later
```
npm install node-forge@1.4.1
```

Technical details

The vulnerability exists in forge.tls.createConnection() where the library fails to properly validate TLS records that interrupt fragmented handshake messages. When a record of unexpected content type interrupts a fragmented handshake, the code throws an uncaught TypeError instead of gracefully rejecting the input. A remote peer can trigger this exception via network packets, causing the connection to terminate or the process to crash.

Affected products

Digital Bazaar Forge prior to 1.4.1

Identifiers

CVE-2026-119188
GHSA-8hrf-8g6f-7xwp

Timeline

2026-10-29: disclosed
2026-10-27: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.