CVE
Create ECDH private key recovery in elliptic curve key agreement
Affects create-ecdh 4.0.4 and below, in the browser.js build used by browser bundlers such as browserify and webpack, when the private key is static or reused. Fixed in 4.0.5.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 4.0.5
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.0.5.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.25% · 16th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 45/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- The share of the registry's downloads of each affected package in the window that were versions inside the affected ranges. Downloads, not users or installs: CI runs and mirrors inflate the counts.
- 100% of create-ecdh downloads last week were affected versions (12.4M).npm, 12.4M downloads in the last 7 days, read Nov 14, 2026
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The browserify create-ecdh package (createECDH) does not check that a peer's public key lies on the correct curve before using it to compute a shared secret, but only in its JavaScript version used by browser bundlers and on Node.js versions without working native support. A remote attacker who can submit public keys to a party that reuses a static private key can exploit this to recover that private key.
Original description
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.
Who should check
Teams shipping create-ecdh 4.0.4 or earlier through browserify or other browser bundlers, or on Node.js without a working native createECDH, where static private keys are reused.
“In create-ecdh 4.0.4 (latest release and master 51b8c81 in browser.js , verified on Node.js v24.14.1)”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach20/20create-ecdh: 12.4M downloads a week
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 90 if added to CISA KEV
- Would score about 85 if CISA's SSVC rates exploitation active
- Would score about 50 if advisories confirm default setups are exposed
Impact
- Widely used
create-ecdh has 12.4m weekly downloads.Source: npmjs.com
What to do
Upgrade to a fixed version: 4.0.5.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129319 (create-ecdh: computeSecret does not validate that the peer public key is on the curve (invalid-curve attack)), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129319 (entry last updated 2026-11-14):
Affected:
- npm package create-ecdh: fixed in 4.0.5
Fixed versions: 4.0.5.
Conditions (all must be true for the bug to be hit):
- create-ecdh 4.0.4 and below (source: https://github.com/browserify/createECDH/security/advisories/GHSA-32q7-f779-hw5r)
- The browser.js implementation, used by browser bundlers (source: https://github.com/browserify/createECDH/security/advisories/GHSA-32q7-f779-hw5r)
- Node.js versions whose native createECDH is missing or does not compute the public key in setPrivateKey (source: https://github.com/browserify/createECDH/security/advisories/GHSA-32q7-f779-hw5r)
- The private key is static or reused (source: https://github.com/browserify/createECDH/security/advisories/GHSA-32q7-f779-hw5r)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129319 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129319 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/browserify/createECDH/security/advisories/GHSA-32q7-f779-hw5r
- https://github.com/browserify/createECDH/commit/1cfaf332773237e5fea4b51a2ad3efab4c22bec1
- https://www.cve.org/CVERecord?id=CVE-2026-129319
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129319
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129319"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- create-ecdhnpm
fixed in 4.0.5
Fixed in 4.0.5 (released Nov 14, 2026, the day of disclosure).
The latest release, 4.0.5, is not affected.
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129319
Is CVE-2026-129319 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
computeSecret does not check that the peer's public key is on the curve. When the private key is static or reused, a low-order point can be submitted, which is the invalid-curve attack named in the title.Source: github.com, cve.org
Which versions are affected by CVE-2026-129319?
create-ecdh (npm): before 4.0.5.Source: cve.now feed data
Am I affected, and how do I check?
create-ecdh 4.0.4 and below is affected, specifically the browser.js implementation used by browser bundlers through the browser field. That path is used where the native crypto.createECDH is missing or does not compute the public key in setPrivateKey. To check the installed version, run npm ls create-ecdh in the project.Source: github.com, cve.org
How do I fix CVE-2026-129319?
Upgrade create-ecdh to 4.0.5 or later.Source: github.com, cve.org