# CVE-2026-118774: Forge: Certificate signature verified with the issuer's RSA signature scheme

Source: https://junglewise.ai/threats/cve-2026-118774-forge-also-called-node-forge-is-a-native-implementation-of  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-29  
License: CC BY 4.0 with a link back

CVE-2026-118774 · Severity: low · CVSS 3.7 · Published 2026-10-29

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used certificate.verify(child), _verifySignature(), lib/x509.js to process the relevant input or security decision. node-forge selected RSA padding and RSASSA-PSS parameters from the issuer certificate rather than the child certificate being verified. A child labeled as RSASSA-PSS could therefore be accepted with a PKCS#1 v1.5 signature when the issuer used PKCS#1 v1.5. The signature still had to be produced with the trusted issuer's private key, so this did not permit certificate identity forgery, but it could bypass policies that require a declared signature scheme. This issue is fixed in version 1.4.1.

Technologies: [node-forge (npm)](https://junglewise.ai/threats/technologies/node-forge). Vendors: [npm](https://junglewise.ai/threats/vendors/npm).

## Quick answers

**Is CVE-2026-118774 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-118774 being exploited in the wild.

**How severe is CVE-2026-118774?** Low severity, with a CVSS score of 3.7, published 29 October 2026.

**Which products and versions are affected?** node-forge (npm) <= 1.4.0, SEMVER:introduced=0,fixed=1.4.1.

**Is there a fix for CVE-2026-118774?** 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.

**Am I affected by CVE-2026-118774?** Check whether you run 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
  ```


## Affected products

- node-forge (npm) <= 1.4.0, SEMVER:introduced=0,fixed=1.4.1

## Identifiers

- CVE-2026-118774
- GHSA-9wg5-mj3p-v49q

## 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 RSA PKCS#1 v1.5 signature forgery via non-canonical DigestInfo encoding](https://junglewise.ai/threats/cve-2026-119192-forge-rsa-pkcs-1-v1-5-signature-forgery-via-non-canonical)