https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-02T10:55:12.188637+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/certfr-2026-avi-0901 certfr-2026-avi-0901 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan… 2026-10-02T10:55:12.193852+00:00 certfr-2026-avi-0901 https://cve.radiocsirt.org/vuln/euvd-2026-265237 EUVD-2026-265237 2026-10-02T10:55:12.193891+00:00 EUVD-2026-265237 https://cve.radiocsirt.org/vuln/fkie_cve-2025-14505 fkie_cve-2025-14505 2026-10-02T10:55:12.193906+00:00

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).

 https://cve.radiocsirt.org/vuln/ghsa-848j-6mx2-7j84 GHSA-848j-6mx2-7j84 — Elliptic Uses a Cryptographic Primitive with a Risky Implementation 2026-10-02T10:55:12.193944+00:00

Affected: npm: elliptic

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).

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-14505 UBUNTU-CVE-2025-14505 2026-10-02T10:55:12.193974+00:00

Affected: Ubuntu:18.04:LTS: node-elliptic, Ubuntu:20.04:LTS: node-elliptic, Ubuntu:22.04:LTS: node-elliptic, Ubuntu:24.04:LTS: node-elliptic, Ubuntu:25.10: node-elliptic, Ubuntu:26.04:LTS: node-elliptic

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).