{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-24412 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-24412 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-24412 is a high-severity memory corruption vulnerability in Color Iccdev, published on 24 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-24412 and fix it if it is affected.\n\nWhat it is: CVE-2026-24412 is a high-severity memory corruption vulnerability in Color Iccdev, published on 24 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-24412 in the wild and no public exploit code.\n\nAffected product: Color Iccdev. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-24412/ (Markdown: https://insights.sbomify.com/CVE-2026-24412/index.md)","id":"CVE-2026-24412","markdown":"https://insights.sbomify.com/CVE-2026-24412/index.md","name":"CVE-2026-24412","record":{"aliases":["GHSA-6rf4-63j2-cfrf"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"ICC color management library","requires_auth":"none","summary":"Heap buffer overflow in iccDEV allows attackers to execute code or cause denial of service via malicious ICC profile data.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"iccdev","vendor":"color"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"},{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"iccDEV provides libraries and tools for interacting with, manipulating, and applying ICC color management profiles. Versions 2.3.1.1 and below have aHeap Buffer Overflow vulnerability in the CIccTagXmlSegmentedCurve::ToXml() function. This occurs when user-controllable input is unsafely incorporated into ICC profile data or other structured binary blobs. Successful exploitation may allow an attacker to perform DoS, manipulate data, bypass application logic and Code Execution. This issue has been fixed in version 2.3.1.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"iccDEV has Heap Buffer Overflow in icCurvesFromXml()","id":"CVE-2026-24412","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"color:iccdev","products":["color:iccdev"],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Icinga has insecure permission of %ProgramData%\\icinga2\\var on Windows","id":"CVE-2026-24413"},"packages":[],"prev":{"headline":"iccDEV has Undefined Behavior and Null Pointer Deference in CIccTagXmlSegmentedCurve::ToXml()","id":"CVE-2026-24411"},"products":["iccDEV"],"published":"2026-01-24","related":[{"cvss_score":9.8,"headline":"iccDEV has a Use After Free vulnerability in CIccCmm class via improper hint manager object deletion","id":"CVE-2026-21675","kev_date_added":null,"published":"2026-01-06"},{"cvss_score":8.8,"headline":"iccDEV has Heap Buffer Overflow in CIccMpeCalculator::Read()","id":"CVE-2026-24405","kev_date_added":null,"published":"2026-01-24"},{"cvss_score":8.8,"headline":"iccDEV has Heap Buffer Overflow in CIccTagNamedColor2::SetSize()","id":"CVE-2026-24406","kev_date_added":null,"published":"2026-01-24"},{"cvss_score":8.8,"headline":"iccDEV has a heap-buffer-overflow in SIccCalcOp::Describe() at IccProfLib/IccMpeCalc.cpp","id":"CVE-2026-22861","kev_date_added":null,"published":"2026-01-13"},{"cvss_score":8.8,"headline":"iccDEV has heap-buffer-overflow in CIccCLUT::Init() at IccProfLib/IccTagLut.cpp","id":"CVE-2026-22255","kev_date_added":null,"published":"2026-01-08"},{"cvss_score":8.8,"headline":"iccDEV has heap-buffer-overflow vulnerability in CIccLocalizedUnicode::GetText()","id":"CVE-2026-21679","kev_date_added":null,"published":"2026-01-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-26","vendors":["InternationalColorConsortium"]},"summary":"Heap buffer overflow in iccDEV allows attackers to execute code or cause denial of service via malicious ICC profile data.","url":"https://insights.sbomify.com/CVE-2026-24412/"}