CVE-2026-21692
Type Confusion in iccDEV ICC Profile Processing Library
Publication date: 2026-01-07
Last updated on: 2026-01-07
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| iccdev | iccdev | to 2.3.1.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-20 | The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. |
| CWE-704 | The product does not correctly convert an object, resource, or structure from one type to a different type. |
| CWE-588 | Casting a non-structure type to a structure type and accessing a field can lead to memory access errors or data corruption. |
| CWE-843 | The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Type Confusion issue in the iccDEV library, specifically in the ToXmlCurve() function located in IccXML/IccLibXML/IccMpeXml.cpp. It affects versions prior to 2.3.1.2 and allows improper handling of ICC color profiles, potentially leading to unexpected behavior or exploitation.
How can this vulnerability impact me? :
The vulnerability can lead to severe impacts including high confidentiality, integrity, and availability risks, as indicated by the CVSS score of 8.8. An attacker could exploit this to cause unauthorized information disclosure, data manipulation, or denial of service when processing ICC color profiles using the affected iccDEV library.
What immediate steps should I take to mitigate this vulnerability?
Upgrade the iccDEV library to version 2.3.1.2 or later, as this version contains the patch for the Type Confusion vulnerability in ToXmlCurve(). No known workarounds are available.