Bug 2458527 (CVE-2026-33021) - CVE-2026-33021 libsixel: libsixel: Use-after-free vulnerability allows for potential code execution via premature pixel buffer freeing.
Summary: CVE-2026-33021 libsixel: libsixel: Use-after-free vulnerability allows for po...
Keywords:
Status: NEW
Alias: CVE-2026-33021
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: 2458614
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-04-14 23: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 23:01:44 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 in sixel_encoder_encode_bytes() because sixel_frame_init() stores the caller-owned pixel buffer pointer directly in frame->pixels without making a defensive copy. When a resize operation is triggered, sixel_frame_convert_to_rgb888() unconditionally frees this caller-owned buffer and replaces it with a new internal allocation, leaving the caller with a dangling pointer. Any subsequent access to the original buffer by the caller constitutes a use-after-free, confirmed by AddressSanitizer. An attacker who controls incoming frames can trigger this bug repeatedly and predictably, resulting in a reliable crash with 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.