Missing public key validation in create-ecdh enables invalid-curve attacks
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- Present
- Impact type
- —
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA.
Summary
The create-ecdh package, a browser implementation of crypto.createECDH, does not validate peer public keys in its JavaScript computeSecret and setPublicKey functions before multiplying them by the local private key (CWE-20). A remote attacker who can submit keys to a party reusing a static private key can mount an invalid-curve or small-subgroup attack and recover the key modulo small factors, then the full key. Low-order points on ed25519 and curve25519 are also accepted, forcing a predictable shared secret. The native implementation on modern Node.js is not affected.
Written with Claude Haiku 5.5 from the sources below · 2026-11-14
Description from the CNA
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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| browserify | createECDH | before 4.0.5 | 4.0.5 | Patch available | CNA |
- createECDH Vendorbrowserify Affected before 4.0.5 Fixed in 4.0.5 Patch available CNA
Remediation
Upgrade create-ecdh to version 4.0.5, which fixes the issue. Versions from 0 before 4.0.5 are affected.
Written with Claude Haiku 5.5 from the sources below · 2026-11-14
- Fix · CNA createECDH (browserify) Fixed in 4.0.5
Timeline
- 2026-11-14 Threatist record created from CVE-2026-129319
References
More browserify vulnerabilities
- TI-2025-08513 Missing type checks leading to hash rewind and passing on crafted data CVSS 4.0CRITICAL 9.1
- TI-2025-08512 Missing type checks leading to hash rewind and passing on crafted data CVSS 4.0CRITICAL 9.1
- TI-2026-65391 pbkdf2 rehashes long passwords on every iteration, enabling denial of service CVSS 4.0MEDIUM 6.3
- TI-2023-24861 browserify-sign vulnerable via an upper bound check issue in `dsaVerify` that leads to a signature forgery attack CVSS 3.1HIGH 7.5
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences