# CVE-2026-119192: Forge RSA PKCS#1 v1.5 signature forgery via non-canonical DigestInfo encoding

Source: https://junglewise.ai/threats/cve-2026-119192-forge-rsa-pkcs-1-v1-5-signature-forgery-via-non-canonical  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

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](https://junglewise.ai/threats/technologies/digital-bazaar-node-forge), [node-forge (npm)](https://junglewise.ai/threats/technologies/node-forge). Vendors: [Digital Bazaar](https://junglewise.ai/threats/vendors/digital-bazaar), [npm](https://junglewise.ai/threats/vendors/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

  ```sh
  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

## Related threats

- [Forge: Ed25519 signature verification accepts small-order public keys](https://junglewise.ai/threats/cve-2026-125335-forge-also-called-node-forge-is-a-native-implementation-of)
- [Forge TLS client crash on handshake record without session](https://junglewise.ai/threats/cve-2026-125334-forge-also-called-node-forge-is-a-native-implementation-of)
- [Forge HTTP ReDoS in response header parsing](https://junglewise.ai/threats/cve-2026-125333-forge-also-called-node-forge-is-a-native-implementation-of)
- [Forge TLS client crash on unsupported ServerHello compression](https://junglewise.ai/threats/cve-2026-125332-forge-also-called-node-forge-is-a-native-implementation-of)
- [Forge ASN.1 BIT STRING decoding recursion exhaustion](https://junglewise.ai/threats/cve-2026-119191-forge-also-called-node-forge-is-a-native-implementation-of)