Is CVE-2026-119191 exploited in the wild?

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

How severe is CVE-2026-119191?

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-119191?

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

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

Am I affected by CVE-2026-119191?

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-119191: Forge ASN.1 BIT STRING decoding recursion exhaustion

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

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

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

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

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

Forge is a JavaScript library that implements cryptographic protocols like TLS. A flaw in ASN.1 parsing allows attackers to send specially crafted data that bypasses recursion limits, causing excessive CPU use and memory consumption. This can lead to denial of service, making applications using Forge unresponsive or crash.

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

Quick answers

Is CVE-2026-119191 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-119191 being exploited in the wild.
How severe is CVE-2026-119191?: 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-119191?: 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-119191 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-119191?: 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 is an uncontrolled recursion (CWE-674) in ASN.1 BIT STRING decoding within asn1.fromDer(). The maxDepth recursion limit was not consistently applied when decoding ASN.1 structures nested inside BIT STRING values, and nested decoding retained full copies at each level causing quadratic memory consumption. A remote unauthenticated attacker can send crafted DER-encoded data with nested BIT STRINGs to trigger excessive recursion and resource exhaustion.

Affected products

Digital Bazaar Forge prior to 1.4.1

Identifiers

CVE-2026-119191
GHSA-rhr8-3pm8-cq29

Timeline

2026-10-29: disclosed

References

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