The load_pnm function in frompnm.c in libsixel.a in libsixel 1.8.2 has infinite recursion.

published 2019-04-08 7y ago modified 2026-06-17 4mo ago also EUVD-2019-2733

cvss: 5.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.0%; EPSS 1.0% chance of exploitation in 30 days, percentile 61%
public exploits: 0; none known

Patch / fix

distros 1

libsixel Debian 14, Debian 13, Debian 12 1.8.6-1

debian advisories DEBIAN-CVE-2019-11024

Is CVE-2019-11024 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.95% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

github.com https://github.com/saitoha/libsixel/issues/85 referenced PoC, tagged "exploit" by a source, unverified
research.loginsoft.com https://research.loginsoft.com/bugs/1501/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.0	5.5	CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness

CWE-674 Uncontrolled Recursion

References

github.com /saitoha/libsixel/issues/85
exploit, third-party-advisory
research.loginsoft.com /bugs/1501/
exploit, third-party-advisory

Sources

CVE List CVE-2019-11024
NVD CVE-2019-11024

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.