Security readout for executives and security teams
Plain-English summary
CVE-2026-22047 is a high-severity memory-safety flaw in iccDEV, a library used to handle ICC color profiles. If an affected application processes a malicious profile, it may crash or allow broader compromise. The vendor advisory says versions before 2.3.1.2 are affected and 2.3.1.2 contains the patch.
Executive priority
Prioritize remediation for internet-facing or user-facing systems that process images, documents, or color profiles using iccDEV. The business risk is highest where untrusted files are accepted. If iccDEV is only used in controlled internal workflows, urgency may be lower but still warrants planned patching.
Technical view
The issue is a heap-buffer-overflow in SIccCalcOp::Describe() in IccProfLib/IccMpeCalc.cpp. It affects iccDEV versions earlier than 2.3.1.2 when processing ICC color profiles. CVSS 3.1 is 8.8 with network attack vector, low complexity, no privileges, and user interaction required.
Likely exposure
Exposure is most likely in products, services, or internal tools that embed iccDEV and accept or process ICC profiles from users, files, uploads, or external content. Systems not using iccDEV, or already on 2.3.1.2 or later, are not indicated as affected by the provided sources.
Exploitation context
The sources do not report active exploitation, and this CVE is not marked as CISA KEV in the provided bundle. Exploitation would require an affected workflow to process a crafted ICC profile. The advisory lists high confidentiality, integrity, and availability impact, but does not provide public exploit status.
Researcher notes
Evidence names CWE-130, CWE-20, and CWE-252, suggesting length validation, input validation, and unchecked return-value issues contributed. The public bundle identifies the vulnerable function and patch version, but does not include exploit details. Review issue 454 and pull request 459 for fix context without assuming impact beyond the advisory.
Mitigation direction
- Upgrade iccDEV to version 2.3.1.2 or later.
- Identify applications and products that bundle or link iccDEV.
- Avoid processing untrusted ICC profiles until patched where feasible.
- Check the GitHub advisory and pull request for vendor-specific update guidance.
- Monitor downstream vendors for patched releases if iccDEV is embedded.
Validation and detection
- Confirm installed or bundled iccDEV versions across build and runtime environments.
- Review dependency manifests, SBOMs, containers, and statically linked components.
- Verify patched deployments report iccDEV 2.3.1.2 or later.
- Trace file-processing paths that accept ICC profiles from external sources.
- Track remediation evidence against the GitHub advisory and CVE record.
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-130: 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-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 lookupCVE-2026-22047 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
- 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
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:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/InternationalColorConsortium/iccDEV/security/advisories/GHSA-22q7-8347-79m5CVE reference · x_refsource_CONFIRM
- https://github.com/InternationalColorConsortium/iccDEV/issues/454CVE reference · x_refsource_MISC
- https://github.com/InternationalColorConsortium/iccDEV/pull/459CVE 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 Handling of Length Parameter Inconsistency
Improper Handling of Length Parameter Inconsistency represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
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.