<?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>Fri, 16 Oct 2026 10:30:50 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-188212</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-188212</link>
      <description>EUVD-2026-188212</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-188212</guid>
    </item>
    <item>
      <title>fkie_cve-2023-37281</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-37281</link>
      <description>&lt;p&gt;Contiki-NG is an operating system for internet-of-things devices. In versions 4.9 and prior, when processing the various IPv6 header fields during IPHC header decompression, Contiki-NG confirms the received packet buffer contains enough data as needed for that field. But no similar check is done before decompressing the IPv6 address. Therefore, up to 16 bytes can be read out of bounds on the line with the statement `memcpy(&amp;amp;ipaddr-&amp;gt;u8[16 - postcount], iphc_ptr, postcount);`. The value of `postcount` depends on the address compression used in the received packet and can be controlled by the attacker. As a result, an attacker can inject a packet that causes an out-of-bound read. As of time of publication, a patched version is not available. As a workaround, one can apply the changes in Contiki-NG pull request #2509 to patch the system.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Contiki-NG is an operating system for internet-of-things devices. In versions 4.9 and prior, when processing the various IPv6 header fields during IPHC header decompression, Contiki-NG confirms the received packet buffer contains enough data as needed for that field. But no similar check is done before decompressing the IPv6 address. Therefore, up to 16 bytes can be read out of bounds on the line with the statement `memcpy(&amp;amp;ipaddr-&amp;gt;u8[16 - postcount], iphc_ptr, postcount);`. The value of `postcount` depends on the address compression used in the received packet and can be controlled by the attacker. As a result, an attacker can inject a packet that causes an out-of-bound read. As of time of publication, a patched version is not available. As a workaround, one can apply the changes in Contiki-NG pull request #2509 to patch the system.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-37281</guid>
    </item>
    <item>
      <title>gsd-2023-37281</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-37281</link>
      <description>gsd-2023-37281</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-37281</guid>
    </item>
  </channel>
</rss>
