Is CVE-2026-118778 exploited in the wild?

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

How severe is CVE-2026-118778?

Medium severity, with a CVSS score of 5.9, 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-118778?

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

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

Am I affected by CVE-2026-118778?

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-118778: Forge TLS client null pointer dereference in certificate validation

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

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

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

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

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-118778 · Severity: medium · CVSS 5.9 · Published 2026-10-29

Forge is a JavaScript library that implements TLS encryption for secure communications. A malicious TLS server can cause the Forge client to crash by omitting the required server certificate message, resulting in denial of service to applications using Forge for secure connections.

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

Quick answers

Is CVE-2026-118778 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-118778 being exploited in the wild.
How severe is CVE-2026-118778?: Medium severity, with a CVSS score of 5.9, 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-118778?: 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-118778 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-118778?: 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 Forge TLS client implementation has a logic error in certificate validation where it checks the wrong property (`c.serverCertificate` instead of `c.session.serverCertificate`), allowing a malicious TLS server to omit the Certificate message and reach code that dereferences a null certificate. This results in an uncaught exception that terminates the TLS connection or the entire process. The vulnerability affects RSA key exchange during TLS handshakes and requires network-level access from a malicious server or on-path attacker.

Affected products

Digital Bazaar Forge prior to 1.4.1

Identifiers

CVE-2026-118778
GHSA-525v-9gp9-w22h

Timeline

2026-10-29: disclosed

References

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