Integer Overflow in Little CMS CubeSize Causes Potential Memory Corruption

Publication date: 2026-04-18

Last updated on: 2026-05-07

Assigner: MITRE

Description

Little CMS (lcms2) through 2.18 has an integer overflow in CubeSize in cmslut.c because the overflow check is performed after the multiplication.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-04-18

Last Modified

2026-05-07

Generated

2026-07-06

AI Q&A

2026-04-18

EPSS Evaluated

2026-07-05

NVD

CVE-2026-41254

EUVD

EUVD-2026-23668

Affected Vendors & Products

Vendor	Product	Version / Range
littlecms	little_cms	to 2.18 (inc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-696	The product performs multiple related behaviors, but the behaviors are performed in the wrong order in ways that may produce resultant weaknesses.
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 occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

Attack-Flow Graph

Executive Summary

This vulnerability is an integer overflow in Little CMS (lcms2) versions through 2.18. It occurs in the CubeSize function within the cmslut.c file because the check for overflow happens after a multiplication operation, which allows the overflow to occur.

Impact Analysis

The vulnerability has a CVSS base score of 4.0, indicating a low severity impact. It requires local access (AV:L) with high attack complexity (AC:H), no privileges (PR:N), and no user interaction (UI:N). The impact is limited to low confidentiality impact (C:L) and low availability impact (A:L), with no integrity impact (I:N). This means an attacker with local access might cause some limited information disclosure or availability issues.

Hi! I’m here to help you understand CVE-2026-41254. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70