Security readout for executives and security teams
Plain-English summary
CVE-2026-21497 can crash iccDEV when it parses certain ICC color profile tag data. The public record rates this as medium severity because it affects availability, not data confidentiality or integrity. Organizations using iccDEV before 2.3.1.2 should prioritize updating, especially where users or workflows process externally supplied color profiles.
Executive priority
Treat as a routine but time-bound availability fix. It is unlikely to be a breach driver based on current public evidence, but it can disrupt workflows that process color profiles. Prioritize environments handling external ICC files or running automated image/color processing.
Technical view
iccDEV versions before 2.3.1.2 contain a NULL pointer dereference in the unknown tag parser. The CVSS 3.1 score is 5.5: local attack vector, low complexity, no privileges, user interaction required, and high availability impact. Listed weaknesses include CWE-20, CWE-252, and CWE-476. The issue is patched in 2.3.1.2.
Likely exposure
Exposure is most likely in systems, applications, build pipelines, or imaging/color workflows that include iccDEV libraries or tools and process ICC profiles. Products embedding iccDEV may also be exposed, but the provided sources only identify InternationalColorConsortium iccDEV before 2.3.1.2.
Exploitation context
No provided source reports active exploitation, and the CVE is not listed as KEV. The CVSS vector indicates exploitation requires local context and user interaction, such as causing vulnerable software to process problematic ICC profile data. Expected impact is denial of service through process crash, not code execution or data theft.
Researcher notes
The public issue, pull request, and commit indicate a parser robustness fix for unknown ICC tags. Analysis should focus on reachability of iccDEV’s unknown tag parsing in local applications and whether untrusted profiles can reach that code path. Do not assume broader product exposure without confirming embedded iccDEV usage.
Mitigation direction
- Upgrade iccDEV to version 2.3.1.2 or later.
- Check vendor guidance for any downstream products embedding iccDEV.
- Limit processing of untrusted ICC profiles until affected systems are upgraded.
- Rebuild source-based deployments with the patched upstream code.
Validation and detection
- Inventory systems and applications that use iccDEV libraries or tools.
- Confirm installed or bundled iccDEV versions are 2.3.1.2 or later.
- For source builds, verify the upstream fix commit is included.
- Review dependency manifests and container images for older iccDEV copies.
- Monitor affected workflows for crash reports while remediation is pending.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-252: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-21497 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H1.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/InternationalColorConsortium/iccDEV/security/advisories/GHSA-7gv7-cmrv-4j85CVE reference · x_refsource_CONFIRM
- https://github.com/InternationalColorConsortium/iccDEV/issues/374CVE reference · x_refsource_MISC
- https://github.com/InternationalColorConsortium/iccDEV/pull/403CVE reference · x_refsource_MISC
- https://github.com/InternationalColorConsortium/iccDEV/commit/9419cac7f084197941994b8b9d17def204008385CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Unchecked Return Value
Unchecked Return Value represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.