CVE-2026-44637: libsixel: integer overflow in parser
libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. From to 1.8.7-r1, a signed integer overflow in the SIXEL parser's image-buffer doubling loop can lead to an out-of-bounds heap write in sixeldecoderawimpl. context->posx grows by repeatcount on every sixel character with no upper bound check. Once posx approaches INTMAX, the expression "posx + repeatcount" used to size the image buffer overflows signed int. Depending on how the overflow wraps, the resize check that should reject oversized buffers can be bypassed, after which a subsequent write computes a large attacker-influenced offset into image->data and writes past the allocation. Reachable from any caller that decodes attacker-supplied SIXEL data, including img2sixel. This vulnerability is fixed in 1.8.7-r2.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-44637?
CVE-2026-44637 has a medium severity rating due to the potential for an out-of-bounds heap write.
How do I fix CVE-2026-44637?
To mitigate CVE-2026-44637, upgrade libsixel to version 1.8.8 or later where the vulnerability is addressed.
What causes the vulnerability CVE-2026-44637?
The vulnerability CVE-2026-44637 is caused by a signed integer overflow in the SIXEL parser's image-buffer doubling loop.
Which versions of libsixel are affected by CVE-2026-44637?
Libsixel versions up to and including 1.8.7-r1 are affected by CVE-2026-44637.
What are the potential impacts of CVE-2026-44637?
The potential impacts of CVE-2026-44637 include memory corruption and possible execution of arbitrary code.