Bug 2458497 (CVE-2026-33018) - CVE-2026-33018 libsixel: libsixel: Arbitrary code execution via Use-After-Free in GIF processing
Summary: CVE-2026-33018 libsixel: libsixel: Arbitrary code execution via Use-After-Fre...
Keywords:
Status: NEW
Alias: CVE-2026-33018
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2458611
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-04-14 22:01 UTC by OSIDB Bzimport
Modified: 2026-04-15 05:52 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-04-14 22:01:37 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.