<?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>Mon, 12 Oct 2026 17:52:27 +0000</lastBuildDate>
    <item>
      <title>cnvd-2022-04018</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2022-04018</link>
      <description>cnvd-2022-04018</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2022-04018</guid>
    </item>
    <item>
      <title>EUVD-2026-33532</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-33532</link>
      <description>EUVD-2026-33532</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-33532</guid>
    </item>
    <item>
      <title>fkie_cve-2021-45684</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-45684</link>
      <description>&lt;p&gt;An issue was discovered in the flumedb crate through 2021-01-07 for Rust. read_entry may read from uninitialized memory locations.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue was discovered in the flumedb crate through 2021-01-07 for Rust. read_entry may read from uninitialized memory locations.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-45684</guid>
    </item>
    <item>
      <title>GHSA-p46c-w9m3-7qr2 — Use of Uninitialized Resource in flumedb.</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p46c-w9m3-7qr2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: flumedb&lt;/p&gt;
&lt;p&gt;Affected versions of this crate passes an uninitialized buffer to a user-provided Read implementation. There are two of such cases (go_offset_log::read_entry() &amp;amp; offset_log::read_entry()).&lt;/p&gt;
&lt;p&gt;Arbitrary Read implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: flumedb&lt;/p&gt;
&lt;p&gt;Affected versions of this crate passes an uninitialized buffer to a user-provided Read implementation. There are two of such cases (go_offset_log::read_entry() &amp;amp; offset_log::read_entry()).&lt;/p&gt;
&lt;p&gt;Arbitrary Read implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p46c-w9m3-7qr2</guid>
    </item>
    <item>
      <title>gsd-2021-45684</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-45684</link>
      <description>gsd-2021-45684</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-45684</guid>
    </item>
    <item>
      <title>RUSTSEC-2021-0086 — `Read` on uninitialized buffer may cause UB ( `read_entry()` )</title>
      <link>https://cve.radiocsirt.org/vuln/rustsec-2021-0086</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: flumedb&lt;/p&gt;
&lt;p&gt;Affected versions of this crate passes an uninitialized buffer to a user-provided `Read` implementation.
There are two of such cases (`go_offset_log::read_entry()` &amp;amp; `offset_log::read_entry()`).&lt;/p&gt;
&lt;p&gt;Arbitrary `Read` implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer.
Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: flumedb&lt;/p&gt;
&lt;p&gt;Affected versions of this crate passes an uninitialized buffer to a user-provided `Read` implementation.
There are two of such cases (`go_offset_log::read_entry()` &amp;amp; `offset_log::read_entry()`).&lt;/p&gt;
&lt;p&gt;Arbitrary `Read` implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer.
Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rustsec-2021-0086</guid>
    </item>
  </channel>
</rss>
