CVE-2026-34551
Null Pointer Dereference in iccDEV CIccTagLut16::Write Function
Publication date: 2026-03-31
Last updated on: 2026-04-20
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.6 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should update iccDEV to version 2.3.1.6 or later, where the null-pointer dereference issue in CIccTagLut16::Write() has been patched.
Can you explain this vulnerability to me?
This vulnerability is a null-pointer dereference (NPD) in the CIccTagLut16::Write() function of the iccDEV libraries and tools. It occurs when processing a specially crafted ICC color management profile embedded in a TIFF file and extracted during the iccTiffDump process. This flaw can cause the software to crash or behave unexpectedly.
How can this vulnerability impact me? :
The impact of this vulnerability is a potential denial of service (DoS) due to the null-pointer dereference causing the application to crash or become unstable. According to the CVSS score, it requires local access with low privileges and no user interaction, and it does not affect confidentiality or integrity, but it does affect availability.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability described is a null-pointer dereference in iccDEV's handling of ICC color management profiles, which can lead to a denial of service (availability impact). There is no indication that this vulnerability affects confidentiality or integrity of data.
Since the vulnerability does not impact confidentiality or integrity, it is unlikely to directly affect compliance with data protection regulations such as GDPR or HIPAA, which primarily focus on protecting personal data privacy and integrity.
However, the availability impact could indirectly affect compliance if the affected systems are critical for processing or accessing regulated data, as availability is a component of some compliance frameworks.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by processing ICC profiles, especially those embedded in TIFF files, using the iccDEV tools such as iccTiffDump. A specially crafted ICC profile can trigger a null pointer dereference in the CIccTagLut16::Write() function, causing a crash or denial of service.
To detect the vulnerability, you can test your system by running iccTiffDump on suspicious or untrusted ICC profiles and observe if the tool crashes or reports errors related to null pointer dereferences.
A suggested command to test for this vulnerability is:
- iccTiffDump <crafted-icc-profile.icc>
Where <crafted-icc-profile.icc> is a specially crafted ICC profile known to trigger the vulnerability, such as the proof-of-concept profile referenced in the advisory.
If the tool crashes or reports a null pointer dereference error during this operation, your system is vulnerable.
Additionally, fuzz testing tools like AFL++ were used to discover this vulnerability by feeding malformed ICC profiles to iccTiffDump, so similar fuzzing approaches can be employed for detection.