<?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>Tue, 06 Oct 2026 10:55:21 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-280048</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-280048</link>
      <description>EUVD-2026-280048</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-280048</guid>
    </item>
    <item>
      <title>fkie_cve-2026-34608</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-34608</link>
      <description>&lt;p&gt;NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. Prior to version 0.24.10, in NanoMQ&amp;#39;s webhook_inproc.c, the hook_work_cb() function processes nng messages by parsing the message body with cJSON_Parse(body). The body is obtained from nng_msg_body(msg), which is a binary buffer without a guaranteed null terminator. This leads to an out-of-bounds read (OOB read) as cJSON_Parse reads until it finds a \0, potentially accessing memory beyond the allocated buffer (e.g., nng_msg metadata or adjacent heap/stack). The issue is often masked by nng&amp;#39;s allocation padding (extra 32 bytes of zeros for non-power-of-two sizes &amp;lt;1024 or non-aligned). The overflow is reliably triggered when the JSON payload length is a power-of-two &amp;gt;=1024 (no padding added). This issue has been patched in version 0.24.10.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. Prior to version 0.24.10, in NanoMQ&amp;#39;s webhook_inproc.c, the hook_work_cb() function processes nng messages by parsing the message body with cJSON_Parse(body). The body is obtained from nng_msg_body(msg), which is a binary buffer without a guaranteed null terminator. This leads to an out-of-bounds read (OOB read) as cJSON_Parse reads until it finds a \0, potentially accessing memory beyond the allocated buffer (e.g., nng_msg metadata or adjacent heap/stack). The issue is often masked by nng&amp;#39;s allocation padding (extra 32 bytes of zeros for non-power-of-two sizes &amp;lt;1024 or non-aligned). The overflow is reliably triggered when the JSON payload length is a power-of-two &amp;gt;=1024 (no padding added). This issue has been patched in version 0.24.10.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-34608</guid>
    </item>
  </channel>
</rss>
