dbcve.org
IccdevApplication · Color

CVE-2026-21679

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-07
Fix available
A fix is available. Upgrade to 2.3.1.2 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 that allow for the interaction, manipulation, and application of ICC color management profiles. Prior to version 2.3.1.2, iccDEV is vulnerable to heap-buffer-overflow in CIccLocalizedUnicode::GetText(). This issue has been patched in version 2.3.1.2.

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 · moderate confidence

Heap buffer overflow vulnerability in CIccLocalizedUnicode::GetText() in iccDEV libraries (versions prior to 2.3.1.2). The vulnerability allows memory corruption which could lead to arbitrary code execution given the heap nature of the overflow and critical CVSS score.

MitigationUpgrade iccDEV to version 2.3.1.2 or later to obtain the patched libraries; verify no downstream products or integrations are affected by the version change.

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

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. Locate the iccDEV library files
    Search for library files named 'libiccv' or 'iccv' with common library extensions (.so, .dll, .dylib, .a) using: find / -name '*icc*' -type f 2>/dev/null on Linux, or check common installation paths like /usr/lib/, /usr/local/lib/, C:\Windows\System32\ on Windows
    Affected if The library files exist in the system
  2. Identify the installed version of iccDEV
    Check the library version by running: strings <library_file> | grep -i version or strings <library_file> | grep -E '[0-9]+\.[0-9]+\.[0-9]+' or using a tool like 'file' and checking any embedded version info. Also check package managers: dpkg -l | grep icc, rpm -qa | grep icc, or brew list iccdev
    Affected if The version is found to be lower than 2.3.1.2
  3. Identify applications using the iccDEV library
    Run ldd <executable> on Linux or Dependency Walker on Windows to find executables linked against the iccDEV library, or search process memory for strings referencing 'CIccLocalizedUnicode' or 'GetText'
    Affected if Applications or services that parse ICC profiles are linked to the vulnerable library version
  4. Check for ICC profile processing functionality
    Review application logs, configurations, or documentation to determine if the system processes ICC color profiles from untrusted sources. Check for file upload features, image processing pipelines, or print spooler services that handle color profiles
    Affected if The system accepts or processes ICC profile files from users or external sources without validation

A system is affected if it runs any version of iccDEV library prior to 2.3.1.2 and that library is used to process ICC color profiles, particularly from untrusted sources.

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.2 or later
Fixed in 2.3.1.2
Vendor patch github.com →
Interim mitigation

Upgrade iccDEV to version 2.3.1.2 or later to obtain the patched libraries; verify no downstream products or integrations are affected by the version change.

Recommended fix High confidence

2.3.1.2

  1. 1. Identify the current iccDEV version in use by checking your project's dependencies or installed package version
  2. 2. For package manager installations (e.g., if installed via a package manager): Update to version 2.3.1.2 using your package manager's upgrade command
  3. 3. For source installations: Clone or pull the latest iccDEV repository and checkout version 2.3.1.2 using: git checkout 2.3.1.2 or git fetch --tags && git checkout 2.3.1.2
  4. 4. Rebuild and reinstall the library following the project's build instructions
  5. 5. Rebuild any dependent applications that use iccDEV to ensure they link against the updated library
  6. 6. Verify the fix by confirming the library version is 2.3.1.2

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
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
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,864.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21679 — 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-21679 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