https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 23:40:27 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-291652 EUVD-2026-291652 https://cve.radiocsirt.org/vuln/euvd-2026-291652 https://cve.radiocsirt.org/vuln/fkie_cve-2026-33018 <p>libsixel is a SIXEL encoder/decoder implementation derived from kmiya&#39;s sixel. Versions 1.8.7 and prior contain a Use-After-Free vulnerability via the load_gif() function in fromgif.c, where a single sixel_frame_t object is reused across all frames of an animated GIF and gif_init_frame() unconditionally frees and reallocates frame-&gt;pixels between frames without consulting the object&#39;s reference count. Because the public API explicitly provides sixel_frame_ref() to retain a frame and sixel_frame_get_pixels() to access the raw pixel buffer, a callback following this documented usage pattern will hold a dangling pointer after the second frame is decoded, resulting in a heap use-after-free confirmed by ASAN. Any application using sixel_helper_load_image_file() with a multi-frame callback to process user-supplied animated GIFs is affected, with a reliable crash as the minimum impact and potential for code execution. This issue has been fixed in version 1.8.7-r1.</p> <p>libsixel is a SIXEL encoder/decoder implementation derived from kmiya&#39;s sixel. Versions 1.8.7 and prior contain a Use-After-Free vulnerability via the load_gif() function in fromgif.c, where a single sixel_frame_t object is reused across all frames of an animated GIF and gif_init_frame() unconditionally frees and reallocates frame-&gt;pixels between frames without consulting the object&#39;s reference count. Because the public API explicitly provides sixel_frame_ref() to retain a frame and sixel_frame_get_pixels() to access the raw pixel buffer, a callback following this documented usage pattern will hold a dangling pointer after the second frame is decoded, resulting in a heap use-after-free confirmed by ASAN. Any application using sixel_helper_load_image_file() with a multi-frame callback to process user-supplied animated GIFs is affected, with a reliable crash as the minimum impact and potential for code execution. This issue has been fixed in version 1.8.7-r1.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-33018 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-33018 <p><strong>Affected:</strong> 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</p> <p>libsixel is a SIXEL encoder/decoder implementation derived from kmiya&#39;s sixel. Versions 1.8.7 and prior contain a Use-After-Free vulnerability via the load_gif() function in fromgif.c, where a single sixel_frame_t object is reused across all frames of an animated GIF and gif_init_frame() unconditionally frees and reallocates frame-&gt;pixels between frames without consulting the object&#39;s reference count. Because the public API explicitly provides sixel_frame_ref() to retain a frame and sixel_frame_get_pixels() to access the raw pixel buffer, a callback following this documented usage pattern will hold a dangling pointer after the second frame is decoded, resulting in a heap use-after-free confirmed by ASAN. Any application using sixel_helper_load_image_file() with a multi-frame callback to process user-supplied animated GIFs is affected, with a reliable crash as the minimum impact and potential for code execution. This issue has been fixed in version 1.8.7-r1.</p> <p><strong>Affected:</strong> 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</p> <p>libsixel is a SIXEL encoder/decoder implementation derived from kmiya&#39;s sixel. Versions 1.8.7 and prior contain a Use-After-Free vulnerability via the load_gif() function in fromgif.c, where a single sixel_frame_t object is reused across all frames of an animated GIF and gif_init_frame() unconditionally frees and reallocates frame-&gt;pixels between frames without consulting the object&#39;s reference count. Because the public API explicitly provides sixel_frame_ref() to retain a frame and sixel_frame_get_pixels() to access the raw pixel buffer, a callback following this documented usage pattern will hold a dangling pointer after the second frame is decoded, resulting in a heap use-after-free confirmed by ASAN. Any application using sixel_helper_load_image_file() with a multi-frame callback to process user-supplied animated GIFs is affected, with a reliable crash as the minimum impact and potential for code execution. This issue has been fixed in version 1.8.7-r1.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-33018