CVE-2026-30981
Heap Buffer Overflow in iccDEV ICC Profile Library Causes Crash
Publication date: 2026-03-10
Last updated on: 2026-03-13
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| color | iccdev | to 2.3.1.5 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-120 | The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer. |
| CWE-125 | The product reads data past the end, or before the beginning, of the intended buffer. |
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-30981 is a moderate severity vulnerability in the iccDEV package affecting versions prior to 2.3.1.5. It involves a heap-buffer-overflow read in the template class function CIccXmlArrayType<>::DumpArray(), which causes out-of-bounds memory reads. This happens due to improper validation of row and column counts when processing ICC profile data during XML conversion, leading to reading beyond the allocated heap buffer.
The vulnerability can cause application crashes or heap corruption and is triggered when processing crafted ICC profile files with the iccToXml tool. The root cause is insufficient bounds checking in the DumpArray method, which attempts to dump an array of unsigned shorts without verifying buffer sizes properly.
How can this vulnerability impact me? :
This vulnerability can lead to application crashes due to heap-buffer-overflow reads when processing malicious or malformed ICC profile files. The impact includes potential denial of service by crashing the affected application.
Since the vulnerability has a high availability impact (A:H) but low confidentiality impact (C:L) and no integrity impact (I:N), it primarily affects the stability and availability of applications using the iccDEV libraries, rather than compromising data confidentiality or integrity.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the iccDEV tools, specifically the iccToXml tool, with crafted or malformed ICC profile files that trigger the heap-buffer-overflow in the CIccXmlArrayType<>::DumpArray() function.
Fuzz testing with tools like libFuzzer using a specially crafted ICC file (e.g., the file named hbo-CIccXmlArrayType-icTagTypeSignature-IccUtilXml_cpp-Line869.icc) can trigger the vulnerability and cause an AddressSanitizer error indicating a heap-buffer-overflow.
No specific detection commands are provided in the resources, but running iccToXml on suspicious or untrusted ICC profile files and monitoring for crashes or sanitizer errors can help identify the vulnerability.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to upgrade the iccDEV package to version 2.3.1.5 or later, where the vulnerability has been fixed by validating matrix dimensions before processing to prevent out-of-bounds memory access.
If upgrading is not immediately possible, avoid processing untrusted or malformed ICC profile files with the affected versions of iccDEV tools, especially iccToXml, to reduce the risk of triggering the heap-buffer-overflow.
No workarounds are provided in the resources, so updating to the fixed version is the recommended action.