Little CMS up to 2.18 ParseCube cmscgats.c integer overflow

Summaryinfo

A vulnerability has been found in Little CMS up to 2.18 and classified as problematic. Affected is an unknown function of the file cmscgats.c of the component ParseCube. The manipulation leads to integer overflow. This vulnerability is listed as CVE-2026-42798. The attack must be carried out locally. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Little CMS up to 2.18 and classified as problematic. This issue affects an unknown part of the file cmscgats.c of the component ParseCube. The manipulation with an unknown input leads to a integer overflow vulnerability. Using CWE to declare the problem leads to CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-42798 since 04/30/2026. The exploitation is known to be difficult. An attack has to be approached locally. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 313713 (Debian dsa-6262 : liblcms2-2 - security update), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 2.19 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 6a686019825a89b715d16671f18d049523354176 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (313713). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Content Management System

Vendor

• Little

Name

• CMS

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9
• 2.10
• 2.11
• 2.12
• 2.13
• 2.14
• 2.15
• 2.16
• 2.17
• 2.18

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion