Skip to main content
VulnerabilityPublished

CVE-2026-33023: saitoha libsixel · Use After Free

Affects saitoha libsixelSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.8 High : upgrade to 1.8.7-r1 soon.

Data as of 30 Oct 2026, 11:52 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Apr 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-r1.

Affected software

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

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

AI-suggested

This vulnerability has been fixed in libsixel version 1.8.7-r1. Users and developers should upgrade to this version or later to remediate the issue. Since this is not a cloud service, remediation depends on updating the affected software. Patch status is not explicitly confirmed beyond the stated fixed version; verify with the vendor or project repository for the latest updates.

Description

libsixel versions prior to 1.8.7-r1, when built with the --with-gdk-pixbuf2 option, contain a use-after-free vulnerability in the load_with_gdkpixbuf() function. This occurs because the cleanup code incorrectly frees a reference-counted object without respecting its reference count, leading to dangling pointers. An attacker can exploit this by supplying a crafted image to trigger memory corruption, potentially resulting in information disclosure or code execution. The issue has been fixed in version 1.8.7-r1.

References

Community reviews

Loading reviews…