Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2026-25634 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 9th 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-16 (Memory Protection) — 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-25634 affects the iccDEV library, a set of libraries and tools for interacting with, manipulating, and applying ICC color management profiles. In versions prior to 2.3.1.4, the SrcPixel and DestPixel stack buffers overlap in the CIccTagMultiProcessElement::Apply() function in IccTagMPE.cpp. This issue is associated with CWEs including CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), CWE-123 (Write-what-where Condition), CWE-628 (Function Call with Incorrectly Specified Arguments), CWE-682 (Incorrect Calculation of Buffer Size), and CWE-787 (Out-of-bounds Write).
The vulnerability carries 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). An unprivileged local attacker can exploit it with low complexity by tricking a user into processing a specially crafted ICC profile, potentially achieving high confidentiality, integrity, and availability impacts such as arbitrary code execution through buffer manipulation.
Mitigation is available in iccDEV version 2.3.1.4, which includes the fixing commit at https://github.com/InternationalColorConsortium/iccDEV/commit/9206e0b8684e4cf4186d9ae768f16760bc1af9ff. Additional details are provided in the GitHub security advisory at https://github.com/InternationalColorConsortium/iccDEV/security/advisories/GHSA-35rg-jcmp-583h, issue #577 at https://github.com/InternationalColorConsortium/iccDEV/issues/577, pull request #579 at https://github.com/InternationalColorConsortium/iccDEV/pull/579, and release notes at https://github.com/InternationalColorConsortium/iccDEV/releases/tag/v2.3.1.4. Security practitioners should prioritize updating affected iccDEV instances to 2.3.1.4 or later.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-5578
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 2.3.1.4, SrcPixel and DestPixel stack buffers overlap in CIccTagMultiProcessElement::Apply() int IccTagMPE.cpp. This vulnerability is fixed in 2.3.1.4.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 4 hardening rules · 4 OS baselines
V17.3.2V15.2.2
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation directly finds incorrect function calls via static analysis, unit testing, and code review.
Memory-protection mechanisms block unauthorized writes to arbitrary locations even if a write-what-where primitive exists.
Requiring documented development processes, standards, and tools (e.g., compilers, linters) structurally reduces the chance of incorrect argument specification.
Secure engineering principles require memory-safe design and coding that structurally avoids buffer-boundary violations.
Process isolation confines the blast radius of an arbitrary write so it cannot affect other domains.
Input validation directly enforces bounds checking that stops out-of-bounds reads/writes from being introduced or reached.
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 SDLC practices (bounds checking, safe APIs, reviews) directly prevent this class of flaw.
Vulnerability scanning and code analysis directly surface buffer-boundary flaws.
Receiving and triaging vulnerability disclosures commonly includes buffer-related reports.
Developer training on secure coding reduces introduction of memory-buffer errors.
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.
Security testing in development catches out-of-bounds accesses before release, covering most instances of the weakness.
Secure development lifecycle mandates memory-safety practices that directly prevent buffer-boundary violations.
Application security requirements can specify memory-safety rules, but do not prescribe implementation details.
Secure architecture and engineering principles include memory-safe design patterns that mitigate buffer overflows.
Secure coding standards explicitly forbid unsafe buffer operations, directly eliminating CWE-119.
Change management processes help ensure security fixes for such weaknesses are properly deployed.
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-248592 OL 8 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-123
RHEL 8 (1 rule)
- V-230279 RHEL 8 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-123
Windows 10 (1 rule)
- V-220727 Structured Exception Handling Overwrite Protection (SEHOP) must be enabled. prevents CWE-123
Windows 11 (1 rule)
- V-253284 Structured Exception Handling Overwrite Protection (SEHOP) must be enabled. prevents CWE-123