<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: libsixel</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2026-44638: libsixel is a SIXEL encoder/decoder implementation derived from kmiya&#x27;s sixel</title><link>https://patchthecve.com/cve/CVE-2026-44638.html</link><guid>https://patchthecve.com/cve/CVE-2026-44638.html</guid><pubDate>Mon, 26 Oct 2026 14:10:00 +0000</pubDate><description>LOW 2.5: libsixel is a SIXEL encoder/decoder implementation derived from kmiya&#x27;s sixel. From  to 1.8.7-r1, a wrong NULL check after an allocation call in sixel_decode_raw and sixel_decode causes a NULL pointer dereference whenever the allocation fails. The check tests the address of the output parameter (alw</description></item><item><title>CVE-2026-44637: libsixel is a SIXEL encoder/decoder implementation derived from kmiya&#x27;s sixel</title><link>https://patchthecve.com/cve/CVE-2026-44637.html</link><guid>https://patchthecve.com/cve/CVE-2026-44637.html</guid><pubDate>Mon, 26 Oct 2026 14:10:00 +0000</pubDate><description>HIGH 7.1: libsixel is a SIXEL encoder/decoder implementation derived from kmiya&#x27;s sixel. From  to 1.8.7-r1, a signed integer overflow in the SIXEL parser&#x27;s image-buffer doubling loop can lead to an out-of-bounds heap write in sixel_decode_raw_impl. context-&gt;pos_x grows by repeat_count on every sixel character</description></item><item><title>CVE-2026-44636: libsixel is a SIXEL encoder/decoder implementation derived from kmiya&#x27;s sixel</title><link>https://patchthecve.com/cve/CVE-2026-44636.html</link><guid>https://patchthecve.com/cve/CVE-2026-44636.html</guid><pubDate>Mon, 26 Oct 2026 14:10:00 +0000</pubDate><description>HIGH 7.4: libsixel is a SIXEL encoder/decoder implementation derived from kmiya&#x27;s sixel. From  to 1.8.7-r1, signed integer overflow in sixel_encode_highcolor&#x27;s allocation size calculation can lead to a heap buffer overflow. The public sixel_encode entry point validates only that width and height are greater t</description></item></channel></rss>