CVE-2026-129319 Affecting node-create-ecdh package, versions <4.0.5-1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.25% (17th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIAN14-NODECREATEECDH-22550173
  • published15 Nov 2026
  • disclosed14 Nov 2026

Introduced: 14 Nov 2026

NewCVE-2026-129319  (opens in a new tab)

How to fix?

Upgrade Debian:14 node-create-ecdh to version 4.0.5-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream node-create-ecdh package and not the node-create-ecdh package as distributed by Debian. See How to fix? for Debian:14 relevant fixed versions and status.

create-ecdh is a browserifiable implementation of Node.js crypto.createECDH. In versions 4.0.4 and below, the JavaScript implementation (browser.js, used by browser bundlers and on Node.js versions without a working native crypto.createECDH) did not validate peer public keys in ECDH.prototype.computeSecret or ECDH.prototype.setPublicKey. The peer point was multiplied by the local private key without checking that it was on the configured curve or in its prime-order subgroup. An attacker who can submit public keys to a party that reuses a static private key can perform an invalid-curve or small-subgroup attack and recover the private key modulo small factors, eventually recovering the full key via the Chinese Remainder Theorem. For the ed25519 and curve25519 curves, low-order points were also accepted, which could force a predictable shared secret. On modern Node.js, create-ecdh re-exports the native implementation, which is not affected. This issue is fixed in version 4.0.5.