<?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 09:36:38 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-252073</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-252073</link>
      <description>EUVD-2026-252073</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-252073</guid>
    </item>
    <item>
      <title>fkie_cve-2025-58359</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-58359</link>
      <description>&lt;p&gt;ZF FROST is a Rust implementation of FROST (Flexible Round-Optimised Schnorr Threshold signatures). In versions 2.0.0 through 2.1.0, refresh shares with smaller min_signers will reduce security of group. The inability to change min_signers (i.e. the threshold) with the refresh share functionality (frost_core::keys::refresh module) was not made clear to users. Using a smaller value would not decrease the threshold, and attempts to sign using a smaller threshold would fail. Additionally, after refreshing the shares with a smaller threshold, it would still be possible to sign with the original threshold, potentially causing a security loss to the participant&amp;#39;s shares. This issue is fixed in version 2.2.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ZF FROST is a Rust implementation of FROST (Flexible Round-Optimised Schnorr Threshold signatures). In versions 2.0.0 through 2.1.0, refresh shares with smaller min_signers will reduce security of group. The inability to change min_signers (i.e. the threshold) with the refresh share functionality (frost_core::keys::refresh module) was not made clear to users. Using a smaller value would not decrease the threshold, and attempts to sign using a smaller threshold would fail. Additionally, after refreshing the shares with a smaller threshold, it would still be possible to sign with the original threshold, potentially causing a security loss to the participant&amp;#39;s shares. This issue is fixed in version 2.2.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-58359</guid>
    </item>
    <item>
      <title>GHSA-wgq8-vr6r-mqxm — frost-core: refresh shares with smaller min_signers will reduce security of group</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wgq8-vr6r-mqxm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: frost-core&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;It was not clear that it is not possible to change `min_signers` (i.e. the threshold) with the refresh share functionality (`frost_core::keys::refresh` module). Using a smaller value would not decrease the threshold, and attempts to sign using a smaller threshold would fail. Additionally, after refreshing the shares with a smaller threshold, it would still be possible to sign with the original threshold; however, this could cause a security loss to the participant&amp;#39;s shares. We have not determined the exact security implications of doing so and judged simpler to just validate `min_signers`.&lt;/p&gt;
&lt;p&gt;If for some reason you have done a refresh share procedure with a smaller `min_signers` we strongly recommend migrating to a new key.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Updating to 2.2.0 will ensure that the `min_signers` parameter will be validated. However it won&amp;#39;t restore the security of groups refreshed with a smaller `min_signers` parameters.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;You don&amp;#39;t need to update if you don&amp;#39;t use the refresh share functionality, or if you didn&amp;#39;t try to change the `min_signers` parameter using the refresh share functionality.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;Thank you [BlockSec](https://blocksec.com/) for reporting the finding&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: frost-core&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;It was not clear that it is not possible to change `min_signers` (i.e. the threshold) with the refresh share functionality (`frost_core::keys::refresh` module). Using a smaller value would not decrease the threshold, and attempts to sign using a smaller threshold would fail. Additionally, after refreshing the shares with a smaller threshold, it would still be possible to sign with the original threshold; however, this could cause a security loss to the participant&amp;#39;s shares. We have not determined the exact security implications of doing so and judged simpler to just validate `min_signers`.&lt;/p&gt;
&lt;p&gt;If for some reason you have done a refresh share procedure with a smaller `min_signers` we strongly recommend migrating to a new key.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Updating to 2.2.0 will ensure that the `min_signers` parameter will be validated. However it won&amp;#39;t restore the security of groups refreshed with a smaller `min_signers` parameters.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;You don&amp;#39;t need to update if you don&amp;#39;t use the refresh share functionality, or if you didn&amp;#39;t try to change the `min_signers` parameter using the refresh share functionality.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;Thank you [BlockSec](https://blocksec.com/) for reporting the finding&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wgq8-vr6r-mqxm</guid>
    </item>
  </channel>
</rss>
