CVE-2026-25583
Heap Buffer Overflow in iccDEV ICC Profile Processing
Publication date: 2026-02-04
Last updated on: 2026-02-18
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.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
| 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-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
How can this vulnerability impact me? :
The vulnerability has a CVSS base score of 7.8, indicating a high severity. It can lead to a heap buffer overflow which may allow an attacker to cause a denial of service, crash the application, or potentially execute arbitrary code with limited privileges. The impact includes confidentiality, integrity, and availability being highly affected.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade iccDEV to version 2.3.1.3 or later, where the heap buffer overflow issue in CIccFileIO::Read8() has been patched.
Can you explain this vulnerability to me?
This vulnerability is a heap buffer overflow in the iccDEV library, specifically in the CIccFileIO::Read8() function. It occurs when the function processes malformed ICC profile files due to an unchecked fread operation. This means that when reading certain corrupted or malicious ICC color management profile files, the program may write more data into memory than it should, potentially leading to memory corruption.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know