CVE-2026-33019

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 0.3% (17th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2026-22742 (ENISA EUVD)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. Versions 1.8.7 and prior contain an integer overflow leading to an out-of-bounds heap read in the --crop option handling of img2sixel, where positive coordinates up to INT_MAX are accepted without overflow-safe bounds checking. In sixel_encoder_do_clip(), the expression clip_w + clip_x overflows to a large negative value when clip_x is INT_MAX, causing the bounds guard to be skipped entirely, and the unclamped coordinate is passed through sixel_frame_clip() to clip(), which computes a source pointer far beyond the image buffer and passes it to memmove(). An attacker supplying a specially crafted crop argument with any valid image can trigger an out-of-bounds read in the heap, resulting in a reliable crash and potential information disclosure. This issue has been fixed in version 1.8.7-r1.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
48
EG Risk 48/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
17th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 14, 2026

Last Modified

July 25, 2026

Advisory Details (2)

Auto-updated Jun 14, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

integer overflow lead to OOB Read in img2sixel · Advisory · saitoha/libsixel · GitHub

https://github.com/saitoha/libsixel/security/advisories/GHSA-c854-ffg9-g72c
GitHub release Patch Available

v1.8.7-r1 security update

Patch available: saitoha/libsixel v1.8.7-r1

https://github.com/saitoha/libsixel/releases/tag/v1.8.7-r1

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libsixel1.10.3-1 ... 1:1.8.7-r2-1 (12 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libsixel1.10.3-3 ... 1:1.8.7-r2-1 (9 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libsixel1.10.5-1 ... 1:1.8.7-r2-1 (8 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libsixel1.10.5-1 ... 1:1.8.7-6 (7 versions)
  • every version up to 1:1.8.7-r2-1: fixed in 1:1.8.7-r2-1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 204 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 108 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  2. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  4. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  5. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-10-25 14:35 UTCEG score recompute
  7. 2026-10-24 21:01 UTCEG score recompute
  8. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-10-18 03:47 UTCEG score recompute
  15. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-17 15:47 UTCEG score recompute
  17. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-10-12 16:13 UTCEG score recompute
  23. 2026-10-11 19:56 UTCEG score recompute
  24. 2026-10-11 17:09 UTCEG score recompute
  25. 2026-10-11 14:36 UTCEG score recompute
Show 71 more
  1. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-10-10 19:53 UTCOSV refresh
  4. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-09-21 07:19 UTCOSV refresh
  18. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  19. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  20. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  21. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  22. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  23. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  24. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  25. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  26. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  27. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  28. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  29. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  30. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  31. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  32. 2026-09-02 04:58 UTCOSV refresh
  33. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  34. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  35. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  36. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  37. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  38. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  39. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  40. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  41. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  42. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  43. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  44. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  45. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  46. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  47. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  48. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  49. 2026-08-16 06:43 UTCEG score recompute
  50. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  51. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  52. 2026-08-14 04:47 UTCEG score recompute
  53. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  54. 2026-08-12 18:59 UTCEG score recompute
  55. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  56. 2026-08-11 18:53 UTCEG score recompute
  57. 2026-08-11 02:42 UTCEG score recompute
  58. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  59. 2026-08-09 16:44 UTCEG score recompute
  60. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  61. 2026-08-09 04:06 UTCEG score recompute
  62. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  63. 2026-08-08 02:14 UTCEG score recompute
  64. 2026-08-07 13:36 UTCEG score recompute
  65. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  66. 2026-08-05 23:27 UTCEG score recompute
  67. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  68. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  69. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  70. 2026-08-03 21:39 UTCEG score recompute
  71. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.3% · 17th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-33019?
CVE-2026-33019 is a high-severity vulnerability; its CVE record was published on April 14, 2026. libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. Versions 1.8.7 and prior contain an integer overflow leading to an out-of-bounds heap read in the --crop option handling of img2sixel, where positive coordinates up to INTMAX are accepted without overflow-safe bounds…
When was the CVE record for CVE-2026-33019 published?
The CVE record for CVE-2026-33019 was published on April 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 25, 2026; the record at its source may have been updated since.
Is CVE-2026-33019 actively exploited?
CVE-2026-33019 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-33019?
CVE-2026-33019 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-33019?
A fix for CVE-2026-33019 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33019

Explore →

Is Your Infrastructure Affected by CVE-2026-33019?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs