<?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 14:55:25 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-291511</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-291511</link>
      <description>EUVD-2026-291511</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-291511</guid>
    </item>
    <item>
      <title>fkie_cve-2026-33019</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-33019</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 an integer overflow leading to an out-of-bounds heap read in the --crop option handling of img2sixel, where positive coordinates up to INT_MAX are accepted without overflow-safe bounds checking. In sixel_encoder_do_clip(), the expression clip_w + clip_x overflows to a large negative value when clip_x is INT_MAX, causing the bounds guard to be skipped entirely, and the unclamped coordinate is passed through sixel_frame_clip() to clip(), which computes a source pointer far beyond the image buffer and passes it to memmove(). An attacker supplying a specially crafted crop argument with any valid image can trigger an out-of-bounds read in the heap, resulting in a reliable crash and potential information disclosure. 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 an integer overflow leading to an out-of-bounds heap read in the --crop option handling of img2sixel, where positive coordinates up to INT_MAX are accepted without overflow-safe bounds checking. In sixel_encoder_do_clip(), the expression clip_w + clip_x overflows to a large negative value when clip_x is INT_MAX, causing the bounds guard to be skipped entirely, and the unclamped coordinate is passed through sixel_frame_clip() to clip(), which computes a source pointer far beyond the image buffer and passes it to memmove(). An attacker supplying a specially crafted crop argument with any valid image can trigger an out-of-bounds read in the heap, resulting in a reliable crash and potential information disclosure. 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-33019</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-33019</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-33019</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 an integer overflow leading to an out-of-bounds heap read in the --crop option handling of img2sixel, where positive coordinates up to INT_MAX are accepted without overflow-safe bounds checking. In sixel_encoder_do_clip(), the expression clip_w + clip_x overflows to a large negative value when clip_x is INT_MAX, causing the bounds guard to be skipped entirely, and the unclamped coordinate is passed through sixel_frame_clip() to clip(), which computes a source pointer far beyond the image buffer and passes it to memmove(). An attacker supplying a specially crafted crop argument with any valid image can trigger an out-of-bounds read in the heap, resulting in a reliable crash and potential information disclosure. 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 an integer overflow leading to an out-of-bounds heap read in the --crop option handling of img2sixel, where positive coordinates up to INT_MAX are accepted without overflow-safe bounds checking. In sixel_encoder_do_clip(), the expression clip_w + clip_x overflows to a large negative value when clip_x is INT_MAX, causing the bounds guard to be skipped entirely, and the unclamped coordinate is passed through sixel_frame_clip() to clip(), which computes a source pointer far beyond the image buffer and passes it to memmove(). An attacker supplying a specially crafted crop argument with any valid image can trigger an out-of-bounds read in the heap, resulting in a reliable crash and potential information disclosure. 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-33019</guid>
    </item>
  </channel>
</rss>
