dbcve.org
IccdevApplication · Color

CVE-2026-21675

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-06
Fix available
A fix is available. Upgrade to 2.3.1.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
iccDEV provides a set of libraries and tools for working with ICC color management profiles. Versions 2.3.1 and below contain a Use After Free vulnerability in the CIccXform::Create() function, where it deletes the hint. This issue is fixed in version 2.3.1.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

iccDEV versions 2.3.1 and below contain a Use After Free vulnerability in the CIccXform::Create() function where the hint is deleted but subsequently accessed, leading to use of freed memory. This memory corruption issue allows potentially arbitrary code execution given the critical CVSS score.

MitigationUpgrade iccDEV to version 2.3.1.1 or later to obtain the patched version that addresses the Use After Free in CIccXform::Create(). If immediate upgrade is not feasible, restrict access to tools processing untrusted ICC profiles.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IccdevApplication
Affected:< 2.3.1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify iccDEV version
    Locate and inspect the installed iccDEV version using the package manager, binary metadata, or library version information available in your environment
    Affected if The installed version is 2.3.1 or below, or the version cannot be determined as 2.3.1.1 or later
  2. Verify CIccXform component presence
    Check if the CIccXform library or module containing CIccXform::Create() is loaded or present in your iccDEV installation
    Affected if The CIccXform component is present in the installation and the version is below 2.3.1.1
  3. Confirm ICC profile processing activity
    Monitor or inspect logs/configurations for processes that invoke CIccXform::Create() to process ICC color profiles
    Affected if CIccXform::Create() is being called to process ICC profiles in your environment
  4. Assess profile trust level
    Review whether the ICC profiles being processed originate from untrusted or external sources
    Affected if Untrusted or externally-sourced ICC profiles are being processed using the vulnerable function

You are affected if iccDEV version is below 2.3.1.1 and CIccXform::Create() is used to process ICC profiles, particularly untrusted ones.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.3.1.1 or later
Fixed in 2.3.1.1
Vendor patch github.com →
Interim mitigation

Upgrade iccDEV to version 2.3.1.1 or later to obtain the patched version that addresses the Use After Free in CIccXform::Create(). If immediate upgrade is not feasible, restrict access to tools processing untrusted ICC profiles.

Recommended fix High confidence

2.3.1.1

  1. 1. Identify the current version of iccDEV installed in your environment by checking the library binary or build files
  2. 2. Navigate to the official ICC repository or release page at github.com/InternationalColorConsortium/iccDEV
  3. 3. Download the source code or pre-built binaries for version 2.3.1.1
  4. 4. Replace the existing iccDEV installation with the version 2.3.1.1 files
  5. 5. Rebuild any projects that depend on iccDEV if building from source
  6. 6. Verify the CIccXform::Create() function now correctly handles the hint object without use-after-free by testing color profile operations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Iccdev Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21675 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-21675 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data