<?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://db.gcve.eu</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>Wed, 21 Oct 2026 02:37:54 +0000</lastBuildDate>
    <item>
      <title>RUSTSEC-2026-0077 — Incorrect Check of Signer Response Norm During Verification</title>
      <link>https://db.gcve.eu/vuln/rustsec-2026-0077</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: libcrux-ml-dsa&lt;/p&gt;
&lt;p&gt;The ML-DSA verification algorithm as specified in [FIPS 204,
subsection
6.3](https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.204.pdf#subsection.6.3)
requires verifiers to check that the infinity norm of the deserialized
signer response $z$ does not exceed $\gamma_1 - \beta$ (line 13 of
Algorithm 8).
The same check is required to be performed during signature generation.&lt;/p&gt;
&lt;p&gt;libcrux-ml-dsa did not perform this check correctly during signature
verification, accepting signatures with signer response norm above the
allowed maximum value.  The check is correctly performed during
signing.&lt;/p&gt;
&lt;p&gt;## Impact
Applications using libcrux-ml-dsa for signature verification would
have accepted signatures that would be rejected by a conforming
implementation.&lt;/p&gt;
&lt;p&gt;## Mitigation
Starting from version `0.0.8`, signature verification uses the correct
value for $\gamma_1$ in the signer response norm check.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: libcrux-ml-dsa&lt;/p&gt;
&lt;p&gt;The ML-DSA verification algorithm as specified in [FIPS 204,
subsection
6.3](https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.204.pdf#subsection.6.3)
requires verifiers to check that the infinity norm of the deserialized
signer response $z$ does not exceed $\gamma_1 - \beta$ (line 13 of
Algorithm 8).
The same check is required to be performed during signature generation.&lt;/p&gt;
&lt;p&gt;libcrux-ml-dsa did not perform this check correctly during signature
verification, accepting signatures with signer response norm above the
allowed maximum value.  The check is correctly performed during
signing.&lt;/p&gt;
&lt;p&gt;## Impact
Applications using libcrux-ml-dsa for signature verification would
have accepted signatures that would be rejected by a conforming
implementation.&lt;/p&gt;
&lt;p&gt;## Mitigation
Starting from version `0.0.8`, signature verification uses the correct
value for $\gamma_1$ in the signer response norm check.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/rustsec-2026-0077</guid>
    </item>
  </channel>
</rss>
