<?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, 19 Oct 2026 17:12:44 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-06916</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-06916</link>
      <description>bdu:2024-06916</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-06916</guid>
    </item>
    <item>
      <title>EUVD-2026-216896</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-216896</link>
      <description>EUVD-2026-216896</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-216896</guid>
    </item>
    <item>
      <title>fkie_cve-2023-45675</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-45675</link>
      <description>&lt;p&gt;stb_vorbis is a single file MIT licensed library for processing ogg vorbis files. A crafted file may trigger out of bounds write in `f-&amp;gt;vendor[len] = (char)&amp;#39;\0&amp;#39;;`. The root cause is that if the len read in `start_decoder` is `-1` and `len + 1` becomes 0 when passed to `setup_malloc`. The `setup_malloc` behaves differently when `f-&amp;gt;alloc.alloc_buffer` is pre-allocated. Instead of returning `NULL` as in `malloc` case it shifts the pre-allocated buffer by zero and returns the currently available memory block. This issue may lead to code execution.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;stb_vorbis is a single file MIT licensed library for processing ogg vorbis files. A crafted file may trigger out of bounds write in `f-&amp;gt;vendor[len] = (char)&amp;#39;\0&amp;#39;;`. The root cause is that if the len read in `start_decoder` is `-1` and `len + 1` becomes 0 when passed to `setup_malloc`. The `setup_malloc` behaves differently when `f-&amp;gt;alloc.alloc_buffer` is pre-allocated. Instead of returning `NULL` as in `malloc` case it shifts the pre-allocated buffer by zero and returns the currently available memory block. This issue may lead to code execution.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-45675</guid>
    </item>
    <item>
      <title>gsd-2023-45675</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-45675</link>
      <description>gsd-2023-45675</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-45675</guid>
    </item>
    <item>
      <title>OESA-2024-1410 — stb security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1410</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP2: stb&lt;/p&gt;
&lt;p&gt;Single-file public domain libraries for C/C++.&#13;
&#13;
Security Fix(es):&#13;
&#13;
stb_vorbis is a single file MIT licensed library for processing ogg vorbis files. A crafted file may trigger out of bounds write in `f-&amp;amp;gt;vendor[len] = (char)&amp;amp;apos;\0&amp;amp;apos;;`. The root cause is that if the len read in `start_decoder` is `-1` and `len + 1` becomes 0 when passed to `setup_malloc`. The `setup_malloc` behaves differently when `f-&amp;amp;gt;alloc.alloc_buffer` is pre-allocated. Instead of returning `NULL` as in `malloc` case it shifts the pre-allocated buffer by zero and returns the currently available memory block. This issue may lead to code execution.(CVE-2023-45675)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP2: stb&lt;/p&gt;
&lt;p&gt;Single-file public domain libraries for C/C++.&#13;
&#13;
Security Fix(es):&#13;
&#13;
stb_vorbis is a single file MIT licensed library for processing ogg vorbis files. A crafted file may trigger out of bounds write in `f-&amp;amp;gt;vendor[len] = (char)&amp;amp;apos;\0&amp;amp;apos;;`. The root cause is that if the len read in `start_decoder` is `-1` and `len + 1` becomes 0 when passed to `setup_malloc`. The `setup_malloc` behaves differently when `f-&amp;amp;gt;alloc.alloc_buffer` is pre-allocated. Instead of returning `NULL` as in `malloc` case it shifts the pre-allocated buffer by zero and returns the currently available memory block. This issue may lead to code execution.(CVE-2023-45675)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1410</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-45675</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-45675</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: libstb, Ubuntu:22.04:LTS: libstb, Ubuntu:24.04:LTS: libstb, Ubuntu:25.10: libstb, Ubuntu:26.10: libstb, Ubuntu:26.04:LTS: libstb&lt;/p&gt;
&lt;p&gt;stb_vorbis is a single file MIT licensed library for processing ogg vorbis files. A crafted file may trigger out of bounds write in `f-&amp;gt;vendor[len] = (char)&amp;#39;\0&amp;#39;;`. The root cause is that if the len read in `start_decoder` is `-1` and `len + 1` becomes 0 when passed to `setup_malloc`. The `setup_malloc` behaves differently when `f-&amp;gt;alloc.alloc_buffer` is pre-allocated. Instead of returning `NULL` as in `malloc` case it shifts the pre-allocated buffer by zero and returns the currently available memory block. This issue may lead to code execution.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: libstb, Ubuntu:22.04:LTS: libstb, Ubuntu:24.04:LTS: libstb, Ubuntu:25.10: libstb, Ubuntu:26.10: libstb, Ubuntu:26.04:LTS: libstb&lt;/p&gt;
&lt;p&gt;stb_vorbis is a single file MIT licensed library for processing ogg vorbis files. A crafted file may trigger out of bounds write in `f-&amp;gt;vendor[len] = (char)&amp;#39;\0&amp;#39;;`. The root cause is that if the len read in `start_decoder` is `-1` and `len + 1` becomes 0 when passed to `setup_malloc`. The `setup_malloc` behaves differently when `f-&amp;gt;alloc.alloc_buffer` is pre-allocated. Instead of returning `NULL` as in `malloc` case it shifts the pre-allocated buffer by zero and returns the currently available memory block. This issue may lead to code execution.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-45675</guid>
    </item>
  </channel>
</rss>
