VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libsixel: vulnerability history, versions and safety

libsixel is a package in the Debian ecosystem. Vulert records 86 vulnerabilities for it across 12 releases, from Nov -0001 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
86 vulnerabilities recorded U86
i
26 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
8 in the last 12 months

Most recent disclosure 14 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libsixel vulnerabilities

Vulert verdict on libsixel i

Updated on 23 Oct 2026

Careful: 26 of the 86 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 86 vulnerabilities on record across 2026 years, 8 in the last year.

What to do: Plan around the 26 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 86 over 2026 years · 8 in the last year i
  • Latest disclosure 14 May 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 26 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for libsixel, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 12 of 12 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 1
  • 2018 16
  • 2019 30
  • 2020 4
  • 2021 13
  • 2022 12
  • 2025 2
  • 2026 8

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 8 of the 86 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for libsixel

The 5 most severe of 86 vulnerabilities recorded for this package

Search all 86 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-based Buffer Overflow in libsixel 9.8 critical 1.8.6-1 08 Dec 2019
Integer Overflow in libsixel 1.8.2 9.8 critical 1.8.6-1 08 Dec 2019
Heap-based Buffer Overflow in libsixel 9.8 critical 1.8.6-1 08 Dec 2019
Integer Overflow in libsixel 1.8.2 9.8 critical 1.8.6-1 08 Dec 2019
Buffer Overflow Vulnerability in libsixel: CVE-2022-27044 8.8 high No fix published 08 Apr 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About libsixel

Is libsixel safe to use?

Vulert records 86 vulnerabilities for libsixel in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 86 not yet rated. 26 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does libsixel have?

86 vulnerabilities are recorded for libsixel in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 86 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new libsixel vulnerabilities disclosed?

8 vulnerabilities were recorded for libsixel in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of libsixel are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor libsixel for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the libsixel version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.