CVSS 4.0
8.2 highCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NCVE-2026-129319 create-ecdh: computeSecret does not validate that the peer public key is on the curve (invalid-curve attack)
High (8.2) in browserify createecdh. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
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.
Severity
CVSS 3.1
5.9 mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-14. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-20 Improper Input Validation
- OWASP Top 10
- A05:2025 Injection
- Published
- Assigned by
- harborist (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-129319 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-129319?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-129319?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-129319 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-129319)
HTML:
<a href="https://cve.bz/cve/CVE-2026-129319"><img src="https://cve.bz/cve/badge/CVE-2026-129319.svg" alt="CVE-2026-129319"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| browserify createECDH | before 4.0.5 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | node-create-ecdh | no fix listed | DEBIAN-CVE-2026-129319 |
From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.
Attack patterns (CAPEC)
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).