Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2026-30985 is a high-severity Classic Buffer Overflow (CWE-120) 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 7th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
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-30985 is a heap-based buffer overflow write vulnerability in the iccDEV libraries and tools, which are used for working with ICC color management profiles. The flaw resides in the CIccMatrixMath::SetRange() function and affects versions prior to 2.3.1.5, potentially leading to memory corruption or application crashes. It is rated with a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and is associated with CWEs-120 (Buffer Copy without Checking Size), CWE-122 (Heap-based Buffer Overflow), and CWE-787 (Out-of-bounds Write).
The vulnerability can be exploited by a local attacker with no privileges who tricks a user into processing a specially crafted ICC color profile file via an affected iccDEV application. Exploitation requires low complexity and user interaction, such as opening a malicious file. Successful exploitation enables high-impact consequences, including arbitrary code execution, data tampering, or denial of service through memory corruption.
Mitigation is available via the official patch in iccDEV version 2.3.1.5, as detailed in the project's GitHub release notes, security advisory (GHSA-f9wv-cq46-f9wg), associated issue tracker (#621), and pull request (#636). Security practitioners should advise updating to the fixed version and validating ICC profiles from untrusted sources where possible.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-10729
Vulnerability Data
iccDEV provides a set of libraries and tools for working with ICC color management profiles. Prior to 2.3.1.5, there is a heap-based buffer overflow write in CIccMatrixMath::SetRange() causing memory corruption or crash. This vulnerability is fixed in 2.3.1.5.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.2.1V1.4.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and analysis can find missing size checks before deployment.
Input validation directly enforces size checks before buffer copies.
Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.
Engineering principles require bounds checking and safe buffer handling in design.
Memory protection limits the impact of an overflow once it occurs.
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.
Secure-development practices directly require bounds checking and safe memory handling that prevent heap overflows.
Vulnerability identification processes such as code review or scanning detect classic buffer overflows before exploitation.
Routine patching replaces vulnerable code containing unchecked buffer copies with corrected versions.
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.
Secure coding directly requires bounds-checked memory operations, addressing the root cause of CWE-120.
Security testing in development and acceptance can detect buffer overflows through fuzzing and static analysis, though it does not prevent them at the source.
Secure development life cycle mandates processes that can include input validation and bounds checking to prevent buffer overflows.
Application security requirements can specify input-size validation and safe buffer handling to mitigate classic buffer overflows.
Secure system architecture and engineering principles promote defensive coding patterns that reduce the likelihood of unchecked buffer copies.
Change management can enforce review gates that catch unsafe memory operations before deployment.