CVE-2025-14505
ECDSA Signature Fault in Elliptic ≤6.6.1 Enables Key Exposure
Publication date: 2026-01-08
Last updated on: 2026-01-08
Assigner: HeroDevs
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| unknown_vendor | elliptic | to 6.6.1 (inc) |
| unknown_vendor | elliptic | to 6.5.7 (inc) |
| herodevs | nes_for_elliptic | 6.6.3 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-1240 | To fulfill the need for a cryptographic primitive, the product implements a cryptographic algorithm using a non-standard, unproven, or disallowed/non-compliant cryptographic implementation. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is in the Elliptic JavaScript library's ECDSA implementation, where the nonce value 'k' used in signature generation is incorrectly truncated if it has leading zeros. This happens because the byte-length of 'k' is miscalculated during computation following RFC 6979. As a result, signatures generated can be invalid, breaking legitimate transactions or communications. More seriously, if an attacker obtains both a faulty signature from a vulnerable Elliptic version and a correct signature for the same input and key, they may be able to derive the secret private key, leading to key exposure. [1]
How can this vulnerability impact me? :
The vulnerability can cause legitimate transactions or communications that rely on ECDSA signatures to fail due to invalid signatures. More critically, it can lead to secret key exposure if an attacker obtains both a faulty and a correct signature for the same input, allowing them to derive the private key. This compromises the security of cryptographic operations, potentially allowing attackers to impersonate users, forge signatures, or decrypt sensitive data. Users of vulnerable Elliptic versions should revoke any keys used and migrate to patched or alternative implementations to prevent compromise. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by comparing signatures generated by the vulnerable Elliptic library (versions ≤ 6.6.1) against signatures generated by a non-faulty library such as @noble/curves. A proof-of-concept script exists that demonstrates the signature discrepancy. Specifically, you can generate signatures for the same input using both libraries and check for differences, which indicate the presence of the vulnerability. There are no specific network or system commands provided, but running such signature comparison scripts in your environment can help detect the issue. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include migrating away from the vulnerable Elliptic library versions (≤ 6.6.1) to a patched or alternative implementation. HeroDevs provides a patched version called NES for Elliptic v6.6.3, which is a secure drop-in replacement. Additionally, users should revoke and invalidate any cryptographic keys that were used with vulnerable versions to prevent potential secret key exposure. Using commercial support like HeroDevs NES to receive patches and security updates is also recommended. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in the Elliptic library's ECDSA implementation can lead to secret key exposure, which compromises the confidentiality and integrity of cryptographic operations. This exposure risks unauthorized access to sensitive data and communications, potentially violating data protection requirements under standards like GDPR and HIPAA. Organizations using vulnerable versions must revoke affected keys and migrate to patched implementations to maintain compliance and protect sensitive information. [1, 2]