https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-05T23:27:30.568033+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-291652 EUVD-2026-291652 2026-10-05T23:27:30.616269+00:00 EUVD-2026-291652 https://cve.radiocsirt.org/vuln/fkie_cve-2026-33018 fkie_cve-2026-33018 2026-10-05T23:27:30.616304+00:00

libsixel is a SIXEL encoder/decoder implementation derived from kmiya'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->pixels between frames without consulting the object'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.

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-33018 UBUNTU-CVE-2026-33018 2026-10-05T23:27:30.616342+00:00

Affected: 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

libsixel is a SIXEL encoder/decoder implementation derived from kmiya'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->pixels between frames without consulting the object'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.