# CVE-2026-129319: create-ecdh: computeSecret does not validate that the peer public key is on the curve (invalid-curve attack)

> Attackers submitting public keys to parties using create-ecdh can recover private keys via invalid-curve or small-subgroup attacks.

- **Severity:** High 8.2 (`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 in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** Yes (`ECDH.prototype.computeSecret`, `ECDH.prototype.setPublicKey`)
- **Fix available:** Yes
- **Published:** 14 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-129319, GHSA-32q7-f779-hw5r, UBUNTU-CVE-2026-129319

## What is CVE-2026-129319?

CVE-2026-129319 is a high-severity weak cryptography vulnerability in browserify createECDH, published on 14 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-129319?

An affected version is only exploitable if your software calls ECDH.prototype.computeSecret or ECDH.prototype.setPublicKey. Many projects that include it are not exposed.


## How do I fix CVE-2026-129319?

Upgrade to a fixed version.

## Is CVE-2026-129319 being exploited?

There is no known exploitation of CVE-2026-129319 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129319 and fix it if it is affected.

What it is: CVE-2026-129319 is a high-severity weak cryptography vulnerability in browserify createECDH, published on 14 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-129319 in the wild and no public exploit code.
Exposure: An affected version is only exploitable if your software calls ECDH.prototype.computeSecret or ECDH.prototype.setPublicKey. Many projects that include it are not exposed.

Affected product: browserify createECDH. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
   If an affected version is present, also search the code for calls to ECDH.prototype.computeSecret or ECDH.prototype.setPublicKey and report whether any exist.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129319/ (Markdown: https://insights.sbomify.com/CVE-2026-129319/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129319
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129319
- OSV: https://osv.dev/vulnerability/CVE-2026-129319

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129319/
Summaries are generated and may contain mistakes; the official description above is the record.
