Cyber Resilience

CVE-2026-25582

Memory Safety in Color Iccdev ≤ 2.3.1.3

Public PoCMemory Safety
Published
04 February 2026
Modified
18 February 2026
Patch / advisory
View advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0024 15th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-25582 is a high-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Color Iccdev. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 15th 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 SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-25582 is a heap buffer overflow (read) vulnerability in the iccDEV libraries and tools, which enable interaction, manipulation, and application of ICC color management profiles. The issue occurs in the CIccIO::WriteUInt16Float() function during conversion of malformed XML to ICC profiles using the iccFromXml tool. It affects iccDEV versions prior to 2.3.1.3 and is associated with CWEs-119, CWE-122, and CWE-787, earning a CVSS v3.1 base score of 7.8.

The vulnerability can be exploited by a local attacker with no privileges required, though it demands low attack complexity and user interaction, such as tricking a user into processing a specially crafted malicious XML file with iccFromXml. Successful exploitation leads to high impacts on confidentiality, integrity, and availability, potentially enabling heap corruption, arbitrary code execution, or system crashes without changing scope.

Mitigation is available via the patch in iccDEV version 2.3.1.3. The project's GitHub security advisory (GHSA-46hq-fphp-jggf), issue #559, pull request #561, and commit b5e5dd238f609ec1a4efb25674e7fa4bd29d894a detail the fix and resolution. Security practitioners should prioritize updating affected systems to the patched version.

EU & UK References

Vulnerability Data

iccDEV provides a set of libraries and tools that allow for the interaction, manipulation, and application of ICC color management profiles. Prior to version 2.3.1.3, there is a heap buffer overflow (read) vulnerability in CIccIO::WriteUInt16Float() when converting malformed XML to…

more

ICC profiles via iccFromXml tool. This issue has been patched in version 2.3.1.3.

CWE(s)
CWE-119CWE-122CWE-787

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 →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
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-25583Same product: Color Iccdev
CVE-2026-31796Same product: Color Iccdev
CVE-2026-25585Same product: Color Iccdev
CVE-2026-25584Same product: Color Iccdev
CVE-2026-30979Same product: Color Iccdev
CVE-2026-21504Same product: Color Iccdev
CVE-2026-30985Same product: Color Iccdev
CVE-2026-25634Same product: Color Iccdev
CVE-2026-21486Same product: Color Iccdev
CVE-2026-21678Same product: Color Iccdev

Affected Assets

color
iccdev
≤ 2.3.1.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V17.3.2
  • V1.4.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (including fuzzing and memory-error detectors) can discover heap overflows after they have been coded.

SI-10 Information Input Validation good match

Input validation enforces bounds checking on data written to heap buffers, directly stopping the overflow condition from being introduced.

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

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require memory-safe design and coding that structurally avoids buffer-boundary violations.

SI-16 Memory Protection partial match

Memory protection restricts exploitation impact of buffer overflows without eliminating the underlying coding flaw.

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 full match
prevents

Secure-development practices directly require bounds checking and safe memory handling that prevent heap overflows.

ID.RA-01 partial match
prevents

Vulnerability scanning and code analysis directly surface buffer-boundary flaws.

ID.RA-08 partial match
prevents

Receiving and triaging vulnerability disclosures commonly includes buffer-related reports.

PR.AT-02 partial match
prevents

Developer training on secure coding reduces introduction of memory-buffer errors.

PR.PS-02 partial match
prevents

Patching replaces vulnerable code containing buffer-boundary defects.

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 catches out-of-bounds accesses before release, covering most instances of the weakness.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates memory-safety practices that directly prevent buffer-boundary violations.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify memory-safety rules, but do not prescribe implementation details.

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

Secure architecture and engineering principles include memory-safe design patterns that mitigate buffer overflows.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe buffer operations, directly eliminating CWE-119.

A.8.32 Change management partial match
prevents

Change management can enforce review gates that catch unsafe memory operations before deployment.

References