Skip to main content
VulnerabilityPublished

CVE-2026-44638: saitoha libsixel · NULL Pointer Dereference

Affects saitoha libsixelSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.5 Low : upgrade to 1.8.7-r2 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
2.5Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.8.7-r2
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade saitoha libsixel to 1.8.7-r2.

Affected software

ProductAffectedFixed in
saitohalibsixelAffected
  • >=1.0.0 <1.8.7-r2
Fixed in
  • 1.8.7-r2
GitHubsaitoha/libsixelpkg:github/saitoha/libsixelOther threatsAffected
  • =1.8.7-r2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in libsixel version 1.8.7-r2. Users should upgrade to this version or later to remediate the vulnerability. Patch status is confirmed by the vendor's versioning information. No additional mitigation is indicated.

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.

References

Community reviews

Loading reviews…