CVE-2026-42798

MEDIUMNVD 4.04.0—
EchelonGraph scoreMEDIUM confidence

Score 4.0 from GitHub Security Advisory published 2026-04-30. NVD baseline CVSS 4.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.0Exploit: None knownExposed: 0

A fix is available — apply it.

Little CMS (lcms2) 2.16 through 2.18 before 2.19 has an integer overflow in ParseCube in cmscgats.c.

CVSS v3
4.0
EG Score
4.0(medium)
EG Risk
18(Track)
EG Risk 18/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity40% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

April 30, 2026

Last Modified

April 30, 2026

Advisory Details (3)

Auto-updated Aug 2, 2026
Patch available. Sources: github_commit.
generic

oss-security - Re: lcms2 <= 2.18 CubeSize() integer overflow: stock Ubuntu 24.04 Poppler / evince-thumbnailer / OpenJDK crashers (different triggers), no CVE

https://www.openwall.com/lists/oss-security/2026/04/30/8
generic

Comparing lcms2.18...lcms2.19 · mm2/Little-CMS · GitHub

https://github.com/mm2/Little-CMS/compare/lcms2.18...lcms2.19
github_commit Patch Available

commit 6a686019825a (mm2/Little-CMS)

Patch available: mm2/Little-CMS lcms2.19rc2 (contains commit 6a686019825a)

https://github.com/mm2/Little-CMS/commit/6a686019825a89b715d16671f18d049523354176

Vendor Advisories for CVE-2026-42798(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuliblcms2-utils (2.17-1ubuntu0.2) @ resolute2026-06-14ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
lcms22.16-2, 2.16-2+deb13u12.16-2+deb13u2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
lcms22.16-2, 2.17-1, 2.17-1.12.19.1-1—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 189 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-42798?
CVE-2026-42798 is a medium vulnerability published on April 30, 2026. Little CMS (lcms2) 2.16 through 2.18 before 2.19 has an integer overflow in ParseCube in cmscgats.c.
When was CVE-2026-42798 disclosed?
CVE-2026-42798 was first published in the National Vulnerability Database on April 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42798 actively exploited?
CVE-2026-42798 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-42798?
CVE-2026-42798 has a CVSS v3 base score of 4.0 (NVD).
How do I remediate CVE-2026-42798?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42798, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-42798?

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

Start Free Scan →Browse All CVEs