CVE-2026-21494
Heap Buffer Overflow in iccDEV ICC Profile Processing Library
Publication date: 2026-01-06
Last updated on: 2026-01-06
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| internationalcolorconsortium | iccdev | to 2.3.1.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-122 | A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). |
| CWE-125 | The product reads data past the end, or before the beginning, of the intended buffer. |
| CWE-193 | A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-21494 is a heap buffer overflow vulnerability in the iccDEV library, specifically in the CIccTagLut8::Validate() function that processes ICC color profiles. It occurs when the code reads or writes beyond the allocated heap buffer boundaries, causing out-of-bounds reads and off-by-one errors. This flaw affects all versions prior to 2.3.1.2 and was introduced during the initial implementation of the tag parsers and validators. [2]
How can this vulnerability impact me? :
This vulnerability can lead to a denial of service or crash conditions due to the heap buffer overflow. It has a moderate severity with a CVSS score of 6.1. The impact includes low confidentiality loss, no integrity loss, but high availability impact, meaning it can disrupt the availability of the affected system or application. Exploitation requires local access and user interaction but no privileges. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
There are no specific detection commands or network/system detection methods provided for this vulnerability. However, you can check the version of the iccDEV library in use to determine if it is prior to 2.3.1.2, which is vulnerable. For example, running the IccFromXml tool and checking its version string may help, as the debug version string includes the version number. No direct detection commands for the vulnerability itself are provided. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to upgrade the iccDEV library to version 2.3.1.2 or later, which contains the patch for the heap buffer overflow in CIccTagLut8::Validate(). No other workarounds are available. [2]