CVE-2026-44636: CWE-122: Heap-based Buffer Overflow in saitoha libsixel
libsixel versions from 1.4.4 up to but not including 1.8.7-r2 contain a heap-based buffer overflow vulnerability due to a signed integer overflow in allocation size calculation within the sixel_encode_highcolor function. The vulnerability arises because width and height parameters are only validated to be greater than zero, without an upper bound, allowing a multiplication that can overflow and cause an undersized heap allocation. This leads to out-of-bounds writes during encoding. The issue is fixed in version 1.8.7-r2.
AI Analysis
Technical Summary
The libsixel library, used for SIXEL encoding/decoding, has a heap-based buffer overflow vulnerability (CVE-2026-44636) in versions >= 1.4.4 and < 1.8.7-r2. The vulnerability stems from a signed integer overflow in the calculation of allocation size in the sixel_encode_highcolor function. Specifically, the width and height parameters are only checked to be positive but not bounded, and their product is computed as a signed int. If width * height exceeds INT_MAX (~2.15 billion), the multiplication wraps around, causing malloc to allocate a smaller buffer than needed. The encoder then writes beyond the allocated heap buffer, leading to a heap overflow. This can impact confidentiality, integrity, and availability of the affected system. The vulnerability is addressed in libsixel version 1.8.7-r2.
Potential Impact
Successful exploitation of this vulnerability can result in a heap-based buffer overflow, potentially allowing an attacker to corrupt memory, cause a crash, or execute arbitrary code with the privileges of the process using libsixel. The CVSS 3.1 score is 7.4 (High), indicating significant impact to confidentiality, integrity, and availability. However, exploitation requires supplying specially crafted input with very large width and height values, and local access (attack vector is local).
Mitigation Recommendations
A fix is available in libsixel version 1.8.7-r2. Users and maintainers should upgrade to version 1.8.7-r2 or later to remediate this vulnerability. Since no official patch link or advisory is provided, verify the upgrade through the official libsixel project sources. Until upgraded, avoid processing SIXEL images with extremely large dimensions that could trigger the overflow.
CVE-2026-44636: CWE-122: Heap-based Buffer Overflow in saitoha libsixel
Description
libsixel versions from 1.4.4 up to but not including 1.8.7-r2 contain a heap-based buffer overflow vulnerability due to a signed integer overflow in allocation size calculation within the sixel_encode_highcolor function. The vulnerability arises because width and height parameters are only validated to be greater than zero, without an upper bound, allowing a multiplication that can overflow and cause an undersized heap allocation. This leads to out-of-bounds writes during encoding. The issue is fixed in version 1.8.7-r2.
CVSS v3.1
Score 7.4high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The libsixel library, used for SIXEL encoding/decoding, has a heap-based buffer overflow vulnerability (CVE-2026-44636) in versions >= 1.4.4 and < 1.8.7-r2. The vulnerability stems from a signed integer overflow in the calculation of allocation size in the sixel_encode_highcolor function. Specifically, the width and height parameters are only checked to be positive but not bounded, and their product is computed as a signed int. If width * height exceeds INT_MAX (~2.15 billion), the multiplication wraps around, causing malloc to allocate a smaller buffer than needed. The encoder then writes beyond the allocated heap buffer, leading to a heap overflow. This can impact confidentiality, integrity, and availability of the affected system. The vulnerability is addressed in libsixel version 1.8.7-r2.
Potential Impact
Successful exploitation of this vulnerability can result in a heap-based buffer overflow, potentially allowing an attacker to corrupt memory, cause a crash, or execute arbitrary code with the privileges of the process using libsixel. The CVSS 3.1 score is 7.4 (High), indicating significant impact to confidentiality, integrity, and availability. However, exploitation requires supplying specially crafted input with very large width and height values, and local access (attack vector is local).
Mitigation Recommendations
A fix is available in libsixel version 1.8.7-r2. Users and maintainers should upgrade to version 1.8.7-r2 or later to remediate this vulnerability. Since no official patch link or advisory is provided, verify the upgrade through the official libsixel project sources. Until upgraded, avoid processing SIXEL images with extremely large dimensions that could trigger the overflow.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-07T15:30:10.875Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a062b58ec166c07b00deb4a
Added to database: 05/14/2026, 20:06:48 UTC
Last enriched: 05/22/2026, 15:30:55 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 55
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.