Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 15 May 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:saitoha:libsixel:*:*:*:*:*:*:*:* |
Fri, 15 May 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 14 May 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Saitoha
Saitoha libsixel |
|
| Vendors & Products |
Saitoha
Saitoha libsixel |
Thu, 14 May 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | libsixel is a SIXEL encoder/decoder implementation derived from kmiya'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 (always non-NULL) instead of the value the malloc returned. On allocation failure, the function continues and writes through a NULL pointer, crashing the process. This is a denial of service against any caller of these public APIs that hits a low-memory condition. This vulnerability is fixed in 1.8.7-r2. | |
| Title | libsixel: NULL pointer dereference | |
| Weaknesses | CWE-476 CWE-690 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-15T14:18:03.581Z
Reserved: 2026-05-07T15:30:10.875Z
Link: CVE-2026-44638
Updated: 2026-05-15T14:17:56.807Z
Status : Analyzed
Published: 2026-05-14T20:17:08.983
Modified: 2026-05-15T17:54:09.270
Link: CVE-2026-44638
No data.
OpenCVE Enrichment
Updated: 2026-05-14T22:00:09Z