CVE-2026-25503

Color Iccdev type confusion

7.1 HIGHPublic exploitEPSS 0.51%

Published3 Feb 2026

Description

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, type confusion allowed malformed ICC profiles to trigger undefined behavior when loading invalid icImageEncodingType values causing denial of service. This issue has been patched in version 2.3.1.2.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionRequired

ScopeUnchanged

ConfidentialityNone

IntegrityLow

AvailabilityHigh

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

Affected products

Color Iccdev< 2.3.1.2

Remediation

Fixed in

Color Iccdev≥ 2.3.1.2

Patch & vendor advisories

References

https://github.com/InternationalColorConsortium/iccDEV/commit/353e6517a31cb6ac9fdd44ac0103bc2fadb25175Patch
https://github.com/InternationalColorConsortium/iccDEV/issues/539ExploitIssue TrackingVendor Advisory
https://github.com/InternationalColorConsortium/iccDEV/pull/547Issue Tracking
https://github.com/InternationalColorConsortium/iccDEV/security/advisories/GHSA-pf84-4c7q-x764PatchVendor Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-25503 being actively exploited?

CVE-2026-25503 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.51%.

How severe is CVE-2026-25503?

CVE-2026-25503 has a CVSS 3.1 base score of 7.1, rated high. EPSS estimates a 0.51% probability of exploitation.

Which products are affected by CVE-2026-25503?

Affected products include Color Iccdev.

How do I fix CVE-2026-25503?

Upgrade affected software to a fixed version, for example Color Iccdev 2.3.1.2 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-25503 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.