cve.bz

CVE-2026-110601 saitoha libsixel: Out-of-bounds Write

5.8 mediumEPSS 0.2%

Medium (5.8) in saitoha libsixel. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
libsixel before 1.8.7-r1 and 1.9.0 through 1.10.5 contains a heap out-of-bounds write vulnerability in gif_init_frame() in src/fromgif.c, which never checks the GIF transparent color index against the palette size. Attackers can supply a crafted GIF with a small color table and large transparent index, processed with a background color set, to write bytes past the palette buffer, causing heap corruption or crashes.

Severity

CVSS 4.0

5.8 medium
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

6.3 medium
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 15th 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-10-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-787 Out-of-bounds Write
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-110601 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-110601?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-110601?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-110601 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 CNA's record in the CVE List.

ProductAffected
saitoha libsixelbefore 1.8.7-r1
saitoha libsixelfrom 1.9.0 through 1.10.5

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13libsixelno fix listedDEBIAN-CVE-2026-110601
Debian14libsixel1:1.8.7-r2-1DEBIAN-CVE-2026-110601
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morelibsixelno fix listedUBUNTU-CVE-2026-110601

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

References

Check your stackJSON