<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-19T20:17:44.337226+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/bdu:2024-06916</id>
    <title>bdu:2024-06916</title>
    <updated>2026-10-19T20:17:44.342472+00:00</updated>
    <content>bdu:2024-06916</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2024-06916"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-216896</id>
    <title>EUVD-2026-216896</title>
    <updated>2026-10-19T20:17:44.342518+00:00</updated>
    <content>EUVD-2026-216896</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-216896"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2023-45675</id>
    <title>fkie_cve-2023-45675</title>
    <updated>2026-10-19T20:17:44.342537+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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-&gt;vendor[len] = (char)'\0';`. 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-&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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2023-45675"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2023-45675</id>
    <title>gsd-2023-45675</title>
    <updated>2026-10-19T20:17:44.342582+00:00</updated>
    <content>gsd-2023-45675</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2023-45675"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2024-1410</id>
    <title>OESA-2024-1410 — stb security update</title>
    <updated>2026-10-19T20:17:44.342598+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.03-LTS-SP2: stb</p>
<p>Single-file public domain libraries for C/C++.

Security Fix(es):

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;apos;\0&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;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)</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2024-1410"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-45675</id>
    <title>UBUNTU-CVE-2023-45675</title>
    <updated>2026-10-19T20:17:44.342635+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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-&gt;vendor[len] = (char)'\0';`. 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-&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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-45675"/>
  </entry>
</feed>
