iccDEV provides a set of libraries and tools for working with ICC color management profiles. Versions prior to 2.3.2.1…
Summary
Vulnerability reported (CVE-2026-50278). Risk of unauthorized operations or information disclosure. Exploitable via icSigEmbeddedV5ProfileTag.
Original description
The description as published by the source.
iccDEV provides a set of libraries and tools for working with ICC color management profiles. Versions prior to 2.3.2.1 have a CIccEmbedIO::Read8() size_t underflow. The issue arises due to an embedded-profile read defect when parsing ICC profiles containing icSigEmbeddedV5ProfileTag data with icSigEmbeddedProfileType payloads. Version 2.3.2.1 patches the issue. No known workarounds are available.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-50278 has been found.
Attackers can target a specific entry point like icSigEmbeddedV5ProfileTag over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-50278" on the vendor's site.
CVE-2026-50278 — CWE-125 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: icSigEmbeddedV5ProfileTag / icSigEmbeddedProfileType
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Out-of-bounds read (CWE-125) has been reported. Attackers reach the vulnerable code path via icSigEmbeddedV5ProfileTag without authentication.
Check the vendor advisory for the affected versions. Attack surface: icSigEmbeddedV5ProfileTag / icSigEmbeddedProfileType.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。