Is CVE-2026-118779 exploited in the wild?

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

How severe is CVE-2026-118779?

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

Which products and versions are affected?

Digital Bazaar 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-118779?

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

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

Am I affected by CVE-2026-118779?

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-118779: Forge regular expression denial of service in PEM decoding

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

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

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

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

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-118779 · Severity: high · CVSS 7.5 · Published 2026-10-29

Forge (node-forge) is a JavaScript library that handles cryptographic operations and certificate processing. Versions prior to 1.4.1 contain a performance vulnerability in PEM decoding that allows unauthenticated attackers to craft malformed PEM input that consumes excessive CPU and causes denial of service. Any application using Forge to parse certificates or keys from untrusted sources is affected.

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

Quick answers

Is CVE-2026-118779 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-118779 being exploited in the wild.
How severe is CVE-2026-118779?: High severity, with a CVSS score of 7.5, published 29 October 2026.
Which products and versions are affected?: Digital Bazaar 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-118779?: 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-118779 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-118779?: 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 pem.decode() function in lib/pem.js uses inefficient polynomial-time regular expressions (CWE-1333) to search for PEM message boundaries and parse headers. An attacker can supply specially crafted PEM input with missing END lines to trigger catastrophic backtracking, blocking the event loop. The vulnerability affects high-level parsing APIs including pki.certificateFromPem() and pki.privateKeyFromPem().

Affected products

Digital Bazaar Forge before 1.4.1

Identifiers

CVE-2026-118779
GHSA-7wch-p9px-956x

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.