<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 04:00:34 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-14505 — Elliptic Cryptanalysis vulnerability when `k` has leading zeros</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-14505</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Elliptic&lt;/p&gt;
&lt;p&gt;The ECDSA implementation of the Elliptic package generates incorrect signatures if an interim value of &amp;#39;k&amp;#39; (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 &amp;#39;k&amp;#39; 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.&lt;/p&gt;
&lt;p&gt;This issue affects all known versions of Elliptic (at the time of writing, versions less than or equal to 6.6.1).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Elliptic&lt;/p&gt;
&lt;p&gt;The ECDSA implementation of the Elliptic package generates incorrect signatures if an interim value of &amp;#39;k&amp;#39; (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 &amp;#39;k&amp;#39; 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.&lt;/p&gt;
&lt;p&gt;This issue affects all known versions of Elliptic (at the time of writing, versions less than or equal to 6.6.1).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-14505</guid>
    </item>
  </channel>
</rss>
