Monitor vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
7.8

libsixel: Image Processing Code Can Crash or Leak Memory

CVE-2026-33023
Summary

The libsixel library, used by some image-processing applications, has a bug in older versions that can cause a crash or memory leak if a specially crafted image is processed. If you're using one of these applications, update to the latest version of libsixel to fix the problem.

Original title
libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. In versions 1.8.7 and prior, when built with the --with-gdk-pixbuf2 option, a use-after-free vulnerability exists in l...
Original description
libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. In versions 1.8.7 and prior, when built with the --with-gdk-pixbuf2 option, a use-after-free vulnerability exists in load_with_gdkpixbuf() in loader.c. The cleanup path manually frees the sixel_frame_t object and its internal buffers without consulting the reference count, even though the object was created via the refcounted constructor sixel_frame_new() and exposed to the public callback. A callback that calls sixel_frame_ref(frame) to retain a logically valid reference will hold a dangling pointer after sixel_helper_load_image_file() returns, and any subsequent access to the frame or its fields triggers a use-after-free confirmed by AddressSanitizer. The root cause is a consistency failure between two cleanup strategies in the same codebase: sixel_frame_unref() is used in load_with_builtin() but raw free() is used in load_with_gdkpixbuf(). An attacker supplying a crafted image to any application built against libsixel with gdk-pixbuf2 support can trigger this reliably, potentially leading to information disclosure, memory corruption, or code execution. This issue has been fixed in version 1.8.7-r1.
nvd CVSS3.1 7.8
Vulnerability type
CWE-416 Use After Free
Published: 14 Apr 2026 · Updated: 15 Apr 2026 · First seen: 15 Apr 2026