VulnerabilityPublished 31 Mar 2026

CVE-2026-34556: InternationalColorConsortium iccDEV · Out-of-bounds Read

Affects InternationalColorConsortium iccDEVSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.2 Medium : upgrade to 2.3.1.6 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

6.2Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.3.1.6

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade iccDEV and internationalcolorconsortium/iccDEV to 2.3.1.6.

Affected software

Product	Affected	Fixed in
InternationalColorConsortiumiccDEV	Affected <2.3.1.6	Fixed in 2.3.1.6
GitHubinternationalcolorconsortium/iccDEV`pkg:github/internationalcolorconsortium/iccDEV`Other threats	Affected <2.3.1.6	Fixed in 2.3.1.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-34556, organizations should promptly upgrade iccDEV to version 2.3.1.6 or later, where the vulnerability has been patched. Additionally, implement strict validation and sanitization of ICC profiles before processing to detect and reject malformed or suspicious profiles. Restrict access to tools and libraries that process ICC profiles to trusted users and environments to minimize the risk of malicious input. Employ runtime protections such as AddressSanitizer or similar memory error detection tools during development and testing to identify potential memory safety issues. Monitor application logs and crash reports for anomalies related to ICC profile processing to detect exploitation attempts. Where possible, isolate ICC profile processing in sandboxed or containerized environments to limit the impact of crashes or memory corruption. Finally, maintain an inventory of software components using iccDEV to ensure comprehensive patch management and vulnerability tracking.

Description

iccDEV provides a set of libraries and tools for working with ICC color management profiles. Prior to version 2.3.1.6, there is a heap-buffer-overflow (HBO) in icAnsiToUtf8() in the XML conversion path. The issue is triggered by a crafted ICC profile which causes icAnsiToUtf8(std::string&, char const*) to treat an input buffer as a C-string and call operations that rely on strlen()/null-termination. AddressSanitizer reports an out-of-bounds READ of size 115 past a 114-byte heap allocation, with the failure observed while running the iccToXml tool. This issue has been patched in version 2.3.1.6.

Impact

The primary impact of CVE-2026-34556 is on the availability of applications using the vulnerable iccDEV library, as the heap-buffer-overflow can cause crashes or denial of service when processing maliciously crafted ICC profiles. While there is no direct impact on confidentiality or integrity, the disruption of color profile processing workflows can affect organizations relying on accurate color management, such as printing companies, graphic design firms, and digital imaging services. In automated pipelines or batch processing environments, this vulnerability could be leveraged to disrupt operations or cause system instability. Since exploitation requires local access to supply a crafted ICC profile, remote exploitation is unlikely unless combined with other vulnerabilities or social engineering. The absence of known exploits in the wild reduces immediate risk, but unpatched systems remain vulnerable to potential future attacks. Organizations that integrate iccDEV into their software stacks or use tools like iccToXml should consider the operational impact of potential service interruptions and the risk to business continuity.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Apr 2026, 12:11 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats