CVE-2026-129319
validatedZero produced an exploit or a check.GHSA-32q7-f779-hw5r ↗EUVD-2026-125887 ↗
description
The browser JavaScript implementation of npm create-ecdh through 4.0.4 does not properly validate ECDH peer public keys. An attacker able to submit peer keys to a party reusing a static private key may derive information about that key or cause a predictable shared secret. Deployments using modern Node.js native crypto.createECDH are not affected.
mitigation
Upgrade npm create-ecdh to version 4.0.5 or later. Until upgraded, prevent untrusted parties from supplying ECDH public keys to services that reuse static private keys.
fixed in 4.0.5
outcome
Contextual check: a technique exists and was validated, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-11-14 06:48Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-129319
{ "etk_id": "ETK-2026-4449", "cve_id": "CVE-2026-129319", "display_id": "CVE-2026-129319", "ghsa_id": "GHSA-32q7-f779-hw5r", "euvd_id": "EUVD-2026-125887", "status": "published", "anchor_state": "anchored", "title": "Peer public-key validation flaw in create-ecdh", "summary": "The browser JavaScript implementation of npm create-ecdh through 4.0.4 does not properly validate ECDH peer public keys. An attacker able to submit peer keys to a party reusing a static private key may derive information about that key or cause a predictable shared secret. Deployments using modern Node.js native crypto.createECDH are not affected.", "mitigation": "Upgrade npm create-ecdh to version 4.0.5 or later. Until upgraded, prevent untrusted parties from supplying ECDH public keys to services that reuse static private keys.", "vendor": "browserify", "product": "createECDH", "affected": [ { "affected_notes": [], "affected_ranges": [ "<= 4.0.4" ], "ecosystem": "npm", "fixed_versions": [ "4.0.5" ], "package_name": "create-ecdh", "purl": "pkg:npm/create-ecdh" } ], "cwes": [ 20 ], "cvss_score": 8.2, "cvss_src": "cna_vendor", "cvss_vector": "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", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "contextual", "check": true, "check_confidence_basis": "assessed", "exploit": false, "pipeline_minutes": 8.581431583333334, "t0_at": "2026-11-14T06:48:48.653000+00:00", "signals": { "check": { "at": "2026-11-14T07:21:48.416184+00:00", "days": 0.02291392574074074, "is_lower_bound": false, "measured_at": "2026-11-14T06:48:48.653000+00:00", "url": null }, "trigger_signal": { "at": "2026-11-14T06:48:48.653000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-11-14T06:48:48.653000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-129319" } } }
published 2026-11-14 07:13Z
last change 2026-11-14 08:47Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.