# CVE-2026-125335: Forge: Ed25519 signature verification accepts small-order public keys

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

CVE-2026-125335 · Severity: low · CVSS 3.7 · Published 2026-11-10

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.3, ed25519.verify() decodes a public key in crypto_sign_open() without rejecting small-order points or their non-canonical encodings. With S = 0 and a small-order R value, an attacker who can choose the public key can produce signatures that verify for many messages, or all messages with the identity key, without a private key. This can defeat proof-of-possession, attribution, non-repudiation, or deduplication checks that rely on a signature being bound to the message. Keys produced by normal Ed25519 key generation are not small-order, so applications that verify only trusted or internally generated public keys are not affected. This issue is fixed in version 1.4.3.

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

## Quick answers

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

**How severe is CVE-2026-125335?** Low severity, with a CVSS score of 3.7, published 10 November 2026.

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

**Is there a fix for CVE-2026-125335?** Yes. node-forge (npm): upgrade to 1.4.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-125335?** 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.3 or later

  ```sh
  npm install node-forge@1.4.3
  ```


## Affected products

- node-forge (npm) <= 1.4.2, SEMVER:introduced=0,fixed=1.4.3

## Identifiers

- CVE-2026-125335
- GHSA-6889-vf6x-f3g5

## Related threats

- [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)
- [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)