Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2026-30987 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 4th 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-30987 is a stack buffer overflow vulnerability in the iccDEV libraries and tools, which are used for working with ICC color management profiles. The flaw exists in the CIccTagNum<>::GetValues() function in versions prior to 2.3.1.5, potentially leading to stack memory corruption or application crashes. It is associated with CWE-120 (buffer copy without checking size), CWE-121 (stack-based buffer overflow), and CWE-787 (out-of-bounds write).
An unprivileged local attacker can exploit this vulnerability by tricking a user into processing a specially crafted ICC color profile file, as indicated by the CVSS 3.1 vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score 7.8). Successful exploitation requires low complexity and user interaction but no special privileges. Attackers could achieve high impacts, including unauthorized disclosure of sensitive information, modification of data or code, and denial of service through crashes or corruption.
Mitigation is available in iccDEV version 2.3.1.5 and later, which addresses the buffer overflow. Security practitioners should update affected applications using iccDEV libraries to this version or higher. Relevant advisories and fixes are detailed in the project's GitHub security advisory (GHSA-fj57-gfhq-rjqr), issue tracker (#618), pull request (#638), and release notes for v2.3.1.5.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-10733
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 stack buffer overflow in CIccTagNum<>::GetValues() causing stack 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
—
—
- 2 hardening rules · 2 OS baselines
V5.2.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.
Memory-protection mechanisms limit the ability to execute injected code after a stack overflow.
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.
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 enforce bounds checking and input validation that prevent classic buffer 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.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248594 OL 8 must implement address space layout randomization (ASLR) to protect its memory from unauthorized code execution. prevents CWE-121
Oracle Linux 9 (1 rule)
- V-271452 OL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-121