Cyber Resilience

CVE-2026-34553

Color Iccdev ≤ 2.3.1.6

Public PoC
Published
31 March 2026
Modified
20 April 2026
Patch / advisory
View advisory
CVSS Score v3.1 4.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0016 6th percentile
Risk Priority 32 floored blend · peak EPSS

Summary

CVE-2026-34553 is a medium-severity Return of Stack Variable Address (CWE-562) vulnerability in Color Iccdev. Its CVSS base score is 4.0 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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 defect in LUT dump/iteration logic affecting CIccCLUT::Iterate() and output produced by CIccMBB::Describe() (via CLUT dumping). This issue has…

more

been patched in version 2.3.1.6.

CWE(s)
CWE-562CWE-665

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-34548Same product: Color Iccdev
CVE-2026-34550Same product: Color Iccdev
CVE-2026-34534Same product: Color Iccdev
CVE-2026-21676Same product: Color Iccdev
CVE-2026-27691Same product: Color Iccdev
CVE-2026-34539Same product: Color Iccdev
CVE-2026-34535Same product: Color Iccdev
CVE-2026-34555Same product: Color Iccdev
CVE-2026-30978Same product: Color Iccdev
CVE-2026-34540Same product: Color Iccdev

Affected Assets

color
iccdev
≤ 2.3.1.6

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and static/dynamic analysis directly find functions that return stack-variable addresses.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented development standards and tools can embed coding rules that forbid returning addresses of automatic variables.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles include memory-safety and lifetime rules that structurally disallow returning addresses of stack locals.

SC-24 Fail in Known State partial match

Requiring the system to fail to a known state structurally reduces the chance that uninitialized resources remain reachable.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent return of stack addresses via static analysis, code review, and compiler checks.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect use-after-return bugs before release.

A.8.9 Configuration management mostly match
prevents

Configuration management can enforce secure defaults and initialization settings but is not the primary control for code-level initialization.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC practices can catch stack-variable misuse during design and code review.

A.8.27 Secure system architecture and engineering principles partial match
degrades

Secure architecture and engineering principles discourage unsafe stack usage patterns.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prohibit returning addresses of stack variables.

References