Skip to main content
VulnerabilityPublished Updated

CVE-2026-125335: Node node forge · Prior to 1.4.3, ed25519.verify() decodes a public key in crypto_sign_open() without

Affects node-node-forgeSource GCVE Database

0
Compare
Authoritative record:CVE-2026-125335· Low 3.7

Not known to be exploited · CVSS 3.7 Low · fixed in 1.4.3 : update node-node-forge when convenient.

Data as of 13 Nov 2026, 22:37 UTC

CVSS 3.1 base score
3.7Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.13.7
Patch
Available – fixed in 1.4.3
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Ubuntu 22.04 LTSnode-node-forgepkg:deb/ubuntu/node-node-forge?arch=source&distro=jammyOther threatsAffected
  • =0.10.0~dfsg-3
  • =1.2.1~dfsg-2
Fixed in–
Ubuntu 20.04 LTSnode-node-forgepkg:deb/ubuntu/node-node-forge?arch=source&distro=focalOther threatsAffected
  • =0.8.5~dfsg-2
  • =0.9.1~dfsg-1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade node-forge to version 1.4.3 or later where this issue is fixed. Applications that verify only trusted or internally generated public keys are not affected and may not require immediate action.

Description

A vulnerability in node-forge versions prior to 1.4.3 allows an attacker who can choose a public key to produce signatures that verify for many or all messages without possessing the private key. This is due to ed25519.verify() not rejecting small-order points or their non-canonical encodings in crypto_sign_open(). Normal Ed25519 keys are not affected, so applications verifying only trusted keys are not vulnerable. The issue is fixed in version 1.4.3.

References

Community reviews

Loading reviews…