cve.bz

CVE-2026-44638 saitoha libsixel: NULL Pointer Dereference

2.5 lowExploit referenceEPSS 0.1%

Low (2.5) in saitoha libsixel. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

2.5 low
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 3rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-05-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-476 NULL Pointer Dereference
CWE-690 Unchecked Return Value to NULL Pointer Dereference
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-44638 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-44638?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-44638?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-44638 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
saitoha:libsixelfrom 1.0.0 before 1.8.7-r2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13libsixelno fix listedDEBIAN-CVE-2026-44638
Debian14libsixel1:1.8.7-r2-1DEBIAN-CVE-2026-44638
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 5 morelibsixelno fix listedUBUNTU-CVE-2026-44638
openSUSETumbleweedlibsixel1.10.5-3.1openSUSE-SU-2026:12420-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

References

Check your stackJSON