Is CVE-2026-119192 exploited in the wild?

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

How severe is CVE-2026-119192?

High severity, with a CVSS score of 7.5, published 10 November 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-119192?

Yes. node-forge (npm): upgrade to 1.4.1 or later. Until then: Do not use RSA keys with a low public exponent (e=3) for signature verification. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-119192 attacked?

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

Am I affected by CVE-2026-119192?

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-119192: Forge RSA PKCS#1 v1.5 signature forgery via non-canonical DigestInfo encoding

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

Yes. node-forge (npm): upgrade to 1.4.1 or later. Until then: Do not use RSA keys with a low public exponent (e=3) for signature verification. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-119192 attacked?

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

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

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

Forge is a JavaScript library used to create and verify digital signatures on documents and messages. The library accepted non-standard encodings of signature data that allowed attackers to forge RSA signatures without the private key, but only when RSA keys use a low public exponent (e=3). An attacker could forge signatures to impersonate users or tamper with signed documents.

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

Quick answers

Is CVE-2026-119192 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-119192 being exploited in the wild.
How severe is CVE-2026-119192?: High severity, with a CVSS score of 7.5, published 10 November 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-119192?: Yes. node-forge (npm): upgrade to 1.4.1 or later. Until then: Do not use RSA keys with a low public exponent (e=3) for signature verification. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-119192 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-119192?: 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
```

Do not use RSA keys with a low public exponent (e=3) for signature verification.

Technical details

The RSA PKCS#1 v1.5 signature verification in node-forge accepted non-canonical BER encodings of DigestInfo structures, including NULL parameters with content, non-minimal lengths, and padded OID encodings. This permits BERserk-style forgery attacks on RSA keys with low public exponents (e=3) where an attacker can construct a forged signature without the private key. The fix requires strict canonical DER encoding validation of the DigestInfo structure.

Affected products

Digital Bazaar node-forge before 1.4.1

Identifiers

CVE-2026-119192
GHSA-6qrw-m8cv-hcxf

Timeline

2026-11-10: advisory

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