<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-15T13:27:48.497185+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/rustsec-2026-0075</id>
    <title>RUSTSEC-2026-0075 — All-Zero Key Generation on Catastrophic RNG Failure</title>
    <updated>2026-10-15T13:27:48.499083+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: libcrux-ed25519</p>
<p>The libcrux-ed25519 key generation samples Ed25519 secret keys from a
provided CSPRNG in a loop for up to 100 attempts until a non-zero key
is found.  If a non-zero key could not be sampled within 100 attempts
the key generation function would silently continue with an all-zero buffer as
the secret key.</p>
<p>## Impact
This bug only occurs in the event of a catastrophic failure of the
CSPRNG, but would allow anyone to forge signatures under the resulting
static signing key.</p>
<p>## Mitigation
Instead of silently continuing with an all-zero signing key, starting
from version `0.0.7` key generation will error in the case of 100
failed attempts at sampling a valid key.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/rustsec-2026-0075"/>
  </entry>
</feed>
