Is CVE-2026-119187 exploited in the wild?

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

How severe is CVE-2026-119187?

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

Which products and versions are affected?

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

Is there a fix for CVE-2026-119187?

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

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

Am I affected by CVE-2026-119187?

Check whether you run Digital Bazaar Node-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-119187: node-forge TLS stack exhaustion denial of service

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

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

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

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

Check whether you run Digital Bazaar Node-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-119187 · Severity: high · CVSS 7.5 · Published 2026-10-29

node-forge is a JavaScript library that implements TLS encryption for secure communications. Prior to version 1.4.1, the library processed TLS records in a recursive manner, allowing a remote attacker to send thousands of small records in a single input chunk to exhaust the call stack and crash the application, causing a denial of service.

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

Quick answers

Is CVE-2026-119187 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-119187 being exploited in the wild.
How severe is CVE-2026-119187?: High severity, with a CVSS score of 7.5, published 29 October 2026.
Which products and versions are affected?: Digital Bazaar Node-Forge before 1.4.1; node-forge (npm) <= 1.4.0, SEMVER:introduced=0,fixed=1.4.1.
Is there a fix for CVE-2026-119187?: 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-119187 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-119187?: Check whether you run Digital Bazaar Node-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

node-forge's TLS record processing used recursion when handling multiple records in a single process() call, with each record handler invoking process() again for the next buffered record. A remote peer can send many small TLS records (such as heartbeat records) in one chunk, causing stack frame exhaustion. The vulnerability was fixed in version 1.4.1 by converting the recursive record processing to iterative loop-based processing.

Affected products

Digital Bazaar node-forge before 1.4.1

Identifiers

CVE-2026-119187
GHSA-hqq3-7jhf-c5jx

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.