CVE-2026-44637
HighWhat is CVE-2026-44637?
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 sixel_decode_raw_impl. context->pos_x grows by repeat_count on every sixel character with no upper bound check. Once pos_x approaches INT_MAX, the expression "pos_x + repeat_count" 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.
CVSS Vector Breakdown
CVSS 3.1Requires local access — attacker must be logged in or have physical access to the device.
No special conditions required. Exploit can be performed reliably and repeatedly.
No authentication required. Any anonymous user can exploit this vulnerability.
Victim must take an action (e.g. click a link, open a file) for the exploit to succeed.
Exploiting the vulnerability only affects the vulnerable component itself.
No confidentiality impact. Sensitive data is not exposed.
Complete loss of integrity. Attacker can modify any file or data on the component.
Complete denial of service. The component becomes fully unavailable.
FAQ
CVE-2026-44637 has a CVSS score of 7.1/10, rated as High. This is a high severity vulnerability and should be patched as soon as possible.
CVSS (Common Vulnerability Scoring System) rates vulnerability severity from 0.0 to 10.0. CVE-2026-44637 scores 7.1/10 (High). Scores 9.0–10.0 are Critical, 7.0–8.9 are High, 4.0–6.9 are Medium, and below 4.0 are Low.
The list of devices confirmed to be affected by CVE-2026-44637 is shown in the "Affected Devices" section above. Check your firmware version against the vendor security advisory and apply the latest patch.
Apply the latest firmware or software update from the vendor. Check the References section above for official advisories and patch notes. If no patch is available, consider disabling the affected feature or isolating the device from untrusted networks.