<?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>Wed, 07 Oct 2026 21:22:29 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-205487</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-205487</link>
      <description>EUVD-2026-205487</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-205487</guid>
    </item>
    <item>
      <title>fkie_cve-2024-53984</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-53984</link>
      <description>&lt;p&gt;Nanopb is a small code-size Protocol Buffers implementation.  When the compile time option PB_ENABLE_MALLOC is enabled, the message contains at least one field with FT_POINTER field type, custom stream callback is used with unknown stream length. and the pb_decode_ex() function is used with flag PB_DECODE_DELIMITED, then the pb_decode_ex() function does not automatically call pb_release(), like is done for other failure cases. This could lead to memory leak and potential denial-of-service. This vulnerability is fixed in 0.4.9.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Nanopb is a small code-size Protocol Buffers implementation.  When the compile time option PB_ENABLE_MALLOC is enabled, the message contains at least one field with FT_POINTER field type, custom stream callback is used with unknown stream length. and the pb_decode_ex() function is used with flag PB_DECODE_DELIMITED, then the pb_decode_ex() function does not automatically call pb_release(), like is done for other failure cases. This could lead to memory leak and potential denial-of-service. This vulnerability is fixed in 0.4.9.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-53984</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:0400-1 — Security update for nanopb</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:0400-1</link>
      <description>&lt;p&gt;Security update for nanopb&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for nanopb&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:0400-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-53984</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53984</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: nanopb, Ubuntu:22.04:LTS: nanopb, Ubuntu:24.04:LTS: nanopb, Ubuntu:25.10: nanopb, Ubuntu:26.04:LTS: nanopb&lt;/p&gt;
&lt;p&gt;Nanopb is a small code-size Protocol Buffers implementation.  When the compile time option PB_ENABLE_MALLOC is enabled, the message contains at least one field with FT_POINTER field type, custom stream callback is used with unknown stream length. and the pb_decode_ex() function is used with flag PB_DECODE_DELIMITED, then the pb_decode_ex() function does not automatically call pb_release(), like is done for other failure cases. This could lead to memory leak and potential denial-of-service. This vulnerability is fixed in 0.4.9.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: nanopb, Ubuntu:22.04:LTS: nanopb, Ubuntu:24.04:LTS: nanopb, Ubuntu:25.10: nanopb, Ubuntu:26.04:LTS: nanopb&lt;/p&gt;
&lt;p&gt;Nanopb is a small code-size Protocol Buffers implementation.  When the compile time option PB_ENABLE_MALLOC is enabled, the message contains at least one field with FT_POINTER field type, custom stream callback is used with unknown stream length. and the pb_decode_ex() function is used with flag PB_DECODE_DELIMITED, then the pb_decode_ex() function does not automatically call pb_release(), like is done for other failure cases. This could lead to memory leak and potential denial-of-service. This vulnerability is fixed in 0.4.9.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53984</guid>
    </item>
  </channel>
</rss>
