LiveActive security incident?Get immediate response
CVE Record

CVE-2026-21683: iccDEV has Type Confusion in icStatusCMM::CIccEvalCompare::EvaluateProfile()

iccDEV provides a set of libraries and tools that allow for the interaction, manipulation, and application of International Color Consortium (ICC) color management profiles. Versions prior to 2.3.1.2 have a Type Confusion vulnerability in `icStatusCMM::CIccEvalCompare::EvaluateProfile()`. This vulnerability affects users of the iccDEV library who process ICC color profiles. Version 2.3.1.2 contains a patch. No known workarounds are available.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-21683 is a high-severity flaw in iccDEV before 2.3.1.2. Systems using the library to process ICC color profiles may be at risk if a user opens or processes a malicious profile. The vendor reports a patch in 2.3.1.2 and no known workarounds.

Executive priority

Prioritize remediation for products or workflows that process externally supplied color profiles. The vulnerability has high potential impact, but the available sources do not show active exploitation. Patch planning should be prompt, especially for internet-facing or user-submitted content paths.

Technical view

The issue is a type confusion vulnerability in icStatusCMM::CIccEvalCompare::EvaluateProfile(). The CVSS 3.1 score is 8.8 with network attack vector, low complexity, no privileges, and required user interaction. Impact is rated high for confidentiality, integrity, and availability. Affected versions are iccDEV below 2.3.1.2.

Likely exposure

Exposure is most likely where iccDEV is embedded in applications, pipelines, or services that accept or process ICC color profiles from users, partners, or untrusted sources. The CVSS vector requires user interaction, so risk depends on how profiles enter the workflow.

Exploitation context

The provided sources do not state known active exploitation, and this CVE is not marked KEV in the supplied data. The advisory indicates exploitation depends on processing a crafted ICC profile. Public issue and pull request references exist, but source evidence does not establish in-the-wild attacks.

Researcher notes

Key unknowns include downstream products bundling iccDEV and practical exploitability in specific integrations. Validate exposure through dependency analysis and profile-processing paths. Avoid assuming impact in software that does not use vulnerable iccDEV code or does not process ICC profiles.

Mitigation direction

  • Upgrade iccDEV to version 2.3.1.2 or later.
  • Inventory applications and services that bundle or link iccDEV.
  • Limit processing of ICC profiles from untrusted sources where feasible.
  • Check vendor guidance for any additional operational mitigations.

Validation and detection

  • Confirm deployed iccDEV versions are 2.3.1.2 or later.
  • Review software bills of materials for embedded iccDEV usage.
  • Identify workflows that ingest ICC profiles from external parties.
  • Track remediation status for applications using vulnerable iccDEV versions.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2026-21683 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-21683Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
InternationalColorConsortiumiccDEV< 2.3.1.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.