CVE-2026-44636: libsixel: integer overflow in encoder
libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. From to 1.8.7-r1, signed integer overflow in sixelencodehighcolor's allocation size calculation can lead to a heap buffer overflow. The public sixelencode entry point validates only that width and height are greater than zero, with no upper bound. width and height are multiplied as plain int when computing the allocation size for palettedpixels and normalizedpixels. Any caller that asks libsixel to encode a pixel buffer with width times height greater than INTMAX (about 2.15 billion) will hit a wrapped allocation size; under the right wrap, the malloc succeeds with a buffer much smaller than the encoder expects, and the encoder writes past the end of the heap allocation. This vulnerability is fixed in 1.8.7-r2.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-44636?
CVE-2026-44636 has a medium severity rating due to its potential for a heap buffer overflow.
How do I fix CVE-2026-44636?
To fix CVE-2026-44636, update libsixel to version 1.8.8 or later.
What causes CVE-2026-44636?
CVE-2026-44636 is caused by an integer overflow in the allocation size calculation in sixel_encode_highcolor.
Which versions of libsixel are affected by CVE-2026-44636?
Versions of libsixel prior to 1.8.8, specifically up to and including 1.8.7-r1, are affected by CVE-2026-44636.
Is CVE-2026-44636 exploitable?
Yes, CVE-2026-44636 is exploitable, potentially allowing attackers to execute arbitrary code through a heap buffer overflow.