This issue affects all known versions of Elliptic (at the time of writing, versions less than or equal to 6.6.1).
No analysis available yet.
No remediation available yet.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-848j-6mx2-7j84 | Elliptic Uses a Cryptographic Primitive with a Risky Implementation |
Sat, 10 Jan 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Fri, 09 Jan 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Elliptic Project
Elliptic Project elliptic |
|
| Vendors & Products |
Elliptic Project
Elliptic Project elliptic |
Thu, 08 Jan 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 08 Jan 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The ECDSA implementation of the Elliptic package generates incorrect signatures if an interim value of 'k' (as computed based on step 3.2 of RFC 6979 https://datatracker.ietf.org/doc/html/rfc6979 ) has leading zeros and is susceptible to cryptanalysis, which can lead to secret key exposure. This happens, because the byte-length of 'k' is incorrectly computed, resulting in its getting truncated during the computation. Legitimate transactions or communications will be broken as a result. Furthermore, due to the nature of the fault, attackers could–under certain conditions–derive the secret key, if they could get their hands on both a faulty signature generated by a vulnerable version of Elliptic and a correct signature for the same inputs. This issue affects all known versions of Elliptic (at the time of writing, versions less than or equal to 6.6.1). | |
| Title | Elliptic Cryptanalysis vulnerability when `k` has leading zeros | |
| Weaknesses | CWE-1240 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: HeroDevs
Published:
Updated: 2026-01-08T21:22:55.144Z
Reserved: 2025-12-10T22:37:46.175Z
Link: CVE-2025-14505
Updated: 2026-01-08T21:22:52.267Z
Status : Awaiting Analysis
Published: 2026-01-08T21:15:42.023
Modified: 2026-01-13T14:03:46.203
Link: CVE-2025-14505
OpenCVE Enrichment
Updated: 2026-01-09T13:24:18Z
Github GHSA