You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
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.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
Title: libsixel de saitoha, Description: libsixel es una implementación de codificador/decodificador SIXEL derivada del sixel de kmiya. En las versiones 1.8.7 y anteriores, cuando se compila con la opción --with-gdk-pixbuf2, existe una vulnerabilidad de uso después de liberación en load_with_gdkpixbuf() en loader.c. La ruta de limpieza libera manualmente el objeto sixel_frame_t y sus búferes internos sin consultar el recuento de referencias, a pesar de que el objeto fue creado a través del constructor con recuento de referencias sixel_frame_new() y expuesto a la devolución de llamada pública. Una devolución de llamada que llama a sixel_frame_ref(frame) para retener una referencia lógicamente válida mantendrá un puntero colgante después de que sixel_helper_load_image_file() regrese, y cualquier acceso posterior al marco o sus campos activa un uso después de liberación confirmado por AddressSanitizer. La causa raíz es una falla de consistencia entre dos estrategias de limpieza en la misma base de código: sixel_frame_unref() se usa en load_with_builtin() pero free() sin procesar se usa en load_with_gdkpixbuf(). Un atacante que suministre una imagen manipulada a cualquier aplicación compilada contra libsixel con soporte para gdk-pixbuf2 puede activar esto de manera fiable, lo que podría conducir a revelación de información, corrupción de memoria o ejecución de código. Este problema ha sido solucionado en la versión 1.8.7-r1.
New CVE Received from GitHub, Inc.4/14/2026 7:16:27 PM
Action
Type
Old Value
New Value
Added
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.