<?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, 05 Oct 2026 13:28:13 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-291654</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-291654</link>
      <description>EUVD-2026-291654</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-291654</guid>
    </item>
    <item>
      <title>fkie_cve-2026-33021</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-33021</link>
      <description>&lt;p&gt;libsixel is a SIXEL encoder/decoder implementation derived from kmiya&amp;#39;s sixel. Versions 1.8.7 and prior contain a use-after-free vulnerability in sixel_encoder_encode_bytes() because sixel_frame_init() stores the caller-owned pixel buffer pointer directly in frame-&amp;gt;pixels without making a defensive copy. When a resize operation is triggered, sixel_frame_convert_to_rgb888() unconditionally frees this caller-owned buffer and replaces it with a new internal allocation, leaving the caller with a dangling pointer. Any subsequent access to the original buffer by the caller constitutes a use-after-free, confirmed by AddressSanitizer. An attacker who controls incoming frames can trigger this bug repeatedly and predictably, resulting in a reliable crash with potential for code execution. This issue has been fixed in version 1.8.7-r1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;libsixel is a SIXEL encoder/decoder implementation derived from kmiya&amp;#39;s sixel. Versions 1.8.7 and prior contain a use-after-free vulnerability in sixel_encoder_encode_bytes() because sixel_frame_init() stores the caller-owned pixel buffer pointer directly in frame-&amp;gt;pixels without making a defensive copy. When a resize operation is triggered, sixel_frame_convert_to_rgb888() unconditionally frees this caller-owned buffer and replaces it with a new internal allocation, leaving the caller with a dangling pointer. Any subsequent access to the original buffer by the caller constitutes a use-after-free, confirmed by AddressSanitizer. An attacker who controls incoming frames can trigger this bug repeatedly and predictably, resulting in a reliable crash with potential for code execution. This issue has been fixed in version 1.8.7-r1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-33021</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-33021</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-33021</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: libsixel, Ubuntu:18.04:LTS: libsixel, Ubuntu:20.04:LTS: libsixel, Ubuntu:22.04:LTS: libsixel, Ubuntu:24.04:LTS: libsixel, Ubuntu:25.10: libsixel, Ubuntu:26.04:LTS: libsixel&lt;/p&gt;
&lt;p&gt;libsixel is a SIXEL encoder/decoder implementation derived from kmiya&amp;#39;s sixel. Versions 1.8.7 and prior contain a use-after-free vulnerability in sixel_encoder_encode_bytes() because sixel_frame_init() stores the caller-owned pixel buffer pointer directly in frame-&amp;gt;pixels without making a defensive copy. When a resize operation is triggered, sixel_frame_convert_to_rgb888() unconditionally frees this caller-owned buffer and replaces it with a new internal allocation, leaving the caller with a dangling pointer. Any subsequent access to the original buffer by the caller constitutes a use-after-free, confirmed by AddressSanitizer. An attacker who controls incoming frames can trigger this bug repeatedly and predictably, resulting in a reliable crash with potential for code execution. This issue has been fixed in version 1.8.7-r1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: libsixel, Ubuntu:18.04:LTS: libsixel, Ubuntu:20.04:LTS: libsixel, Ubuntu:22.04:LTS: libsixel, Ubuntu:24.04:LTS: libsixel, Ubuntu:25.10: libsixel, Ubuntu:26.04:LTS: libsixel&lt;/p&gt;
&lt;p&gt;libsixel is a SIXEL encoder/decoder implementation derived from kmiya&amp;#39;s sixel. Versions 1.8.7 and prior contain a use-after-free vulnerability in sixel_encoder_encode_bytes() because sixel_frame_init() stores the caller-owned pixel buffer pointer directly in frame-&amp;gt;pixels without making a defensive copy. When a resize operation is triggered, sixel_frame_convert_to_rgb888() unconditionally frees this caller-owned buffer and replaces it with a new internal allocation, leaving the caller with a dangling pointer. Any subsequent access to the original buffer by the caller constitutes a use-after-free, confirmed by AddressSanitizer. An attacker who controls incoming frames can trigger this bug repeatedly and predictably, resulting in a reliable crash with potential for code execution. This issue has been fixed in version 1.8.7-r1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-33021</guid>
    </item>
  </channel>
</rss>
