<?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>Sun, 04 Oct 2026 01:40:27 +0000</lastBuildDate>
    <item>
      <title>bdu:2023-07919</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2023-07919</link>
      <description>bdu:2023-07919</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2023-07919</guid>
    </item>
    <item>
      <title>EUVD-2026-212116</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-212116</link>
      <description>EUVD-2026-212116</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-212116</guid>
    </item>
    <item>
      <title>fkie_cve-2023-1732</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-1732</link>
      <description>&lt;p&gt;When sampling randomness for a shared secret, the implementation of Kyber and FrodoKEM, did not check whether crypto/rand.Read() returns an error. In rare deployment cases (error thrown by the Read() function), this could lead to a predictable shared secret.&lt;/p&gt;
&lt;p&gt;The tkn20 and blindrsa components did not check whether enough randomness was returned from the user provided randomness source. Typically the user provides crypto/rand.Reader, which in the vast majority of cases will always return the right number random bytes. In the cases where it does not, or the user provides a source that does not, the blinding for blindrsa is weak and integrity of the plaintext is not ensured in tkn20.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;When sampling randomness for a shared secret, the implementation of Kyber and FrodoKEM, did not check whether crypto/rand.Read() returns an error. In rare deployment cases (error thrown by the Read() function), this could lead to a predictable shared secret.&lt;/p&gt;
&lt;p&gt;The tkn20 and blindrsa components did not check whether enough randomness was returned from the user provided randomness source. Typically the user provides crypto/rand.Reader, which in the vast majority of cases will always return the right number random bytes. In the cases where it does not, or the user provides a source that does not, the blinding for blindrsa is weak and integrity of the plaintext is not ensured in tkn20.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-1732</guid>
    </item>
    <item>
      <title>GHSA-2q89-485c-9j2x — Improper random reading in CIRCL</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2q89-485c-9j2x</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/cloudflare/circl&lt;/p&gt;
&lt;p&gt;### Impact
When sampling randomness for a shared secret, the implementation of Kyber and FrodoKEM, did not check whether `crypto/rand.Read()` returns an error. In rare deployment cases (error thrown by the `Read()` function), this could lead to a predictable shared secret.&lt;/p&gt;
&lt;p&gt;The tkn20 and blindrsa components did not check whether enough randomness was returned from the user provided randomness source. Typically the user provides `crypto/rand.Reader`, which in the vast majority of cases will always return the right number random bytes. In the cases where it does not, or the user provides a source that does not, the blinding for blindrsa is weak and integrity of the plaintext is not ensured in tkn20.&lt;/p&gt;
&lt;p&gt;### Patches
The fix was introduced in CIRCL v. 1.3.3&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/cloudflare/circl&lt;/p&gt;
&lt;p&gt;### Impact
When sampling randomness for a shared secret, the implementation of Kyber and FrodoKEM, did not check whether `crypto/rand.Read()` returns an error. In rare deployment cases (error thrown by the `Read()` function), this could lead to a predictable shared secret.&lt;/p&gt;
&lt;p&gt;The tkn20 and blindrsa components did not check whether enough randomness was returned from the user provided randomness source. Typically the user provides `crypto/rand.Reader`, which in the vast majority of cases will always return the right number random bytes. In the cases where it does not, or the user provides a source that does not, the blinding for blindrsa is weak and integrity of the plaintext is not ensured in tkn20.&lt;/p&gt;
&lt;p&gt;### Patches
The fix was introduced in CIRCL v. 1.3.3&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2q89-485c-9j2x</guid>
    </item>
    <item>
      <title>gsd-2023-1732</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-1732</link>
      <description>gsd-2023-1732</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-1732</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:14663-1 — velociraptor-0.7.0.4.git142.862ef23-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:14663-1</link>
      <description>&lt;p&gt;velociraptor-0.7.0.4.git142.862ef23-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;velociraptor-0.7.0.4.git142.862ef23-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2025:14663-1</guid>
    </item>
  </channel>
</rss>
