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


- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 10 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-6889-vf6x-f3g5, MINI-56p6-pgc4-f4c7, MINI-65pg-wffw-qp3q, MINI-9mm3-w53q-3mmr, MINI-p23q-whc3-fgv3, MINI-wx5r-rmxm-hw6w, MINI-xq55-vrpp-7c3c, UBUNTU-CVE-2026-125335

## What is CVE-2026-125335?

CVE-2026-125335 is a low-severity vulnerability in digitalbazaar forge, published on 10 Nov 2026. 

### Official description

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.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-125335?

1 open source package ship an affected version, including node-forge.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node-forge` | npm | All versions | 1.4.3 |

## How do I fix CVE-2026-125335?

Upgrade node-forge to 1.4.3 or later.

## Is CVE-2026-125335 being exploited?

There is no known exploitation of CVE-2026-125335 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-125335 and fix it if it is affected.

What it is: CVE-2026-125335 is a low-severity vulnerability in digitalbazaar forge, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125335 in the wild and no public exploit code.

Affected packages and fixed versions:
- node-forge (npm): affected all versions; fixed in 1.4.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-125335/ (Markdown: https://insights.sbomify.com/CVE-2026-125335/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-125335
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-125335
- OSV: https://osv.dev/vulnerability/CVE-2026-125335

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-125335/
Summaries are generated and may contain mistakes; the official description above is the record.