Skip to content
OpenAdvisories
High · 7.3 CVE-2026-33021 EUVD-2026-22746

libsixel: Use-after-free in sixel_encoder_encode_bytes()

Published Apr 14, 2026 · Updated Apr 16, 2026 · Assigned by GitHub_M

Description

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.

Affected products

VendorProductAffectedFixed
saitoha libsixel < 1.8.7-r1 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Debian 14 libsixel 1:1.8.7-r2-1 —
Debian 13 libsixel No fix yet —
Debian 12 libsixel No fix yet —
ReleasePackageFixed inAdvisory
Ubuntu 26.10 libsixel No fix yet —
Ubuntu 26.04 LTS libsixel No fix yet —
Ubuntu 25.10 libsixel No fix yet —
Ubuntu 24.04 LTS libsixel No fix yet —
Ubuntu 22.04 LTS libsixel No fix yet —
Show 3 more (older releases, extended support, other products)
ReleasePackageFixed inAdvisory
Ubuntu 20.04 LTS libsixel No fix yet —
Ubuntu 18.04 LTS libsixel No fix yet —
Ubuntu 16.04 LTS libsixel No fix yet —

References