Quick answers
- Is CVE-2026-82328 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82328 being exploited in the wild.
- How severe is CVE-2026-82328?
- Medium severity, with a CVSS score of 6.1, published 28 August 2026.
- Which products and versions are affected?
- Gimp <unknown.
- Is there a fix for CVE-2026-82328?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-82328 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-82328?
- Check whether you run Gimp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The file-ico plugin in GIMP fails to properly validate the used_clrs (palette count) parameter when parsing ICO image files. This improper validation leads to insufficient memory bounds checking, resulting in a heap out-of-bounds read. The vulnerability is triggered when a specially crafted ICO file is opened in GIMP. An attacker must convince a user to open a malicious ICO file (network reachable via file download, or local via file sharing). Successful exploitation results in application crash (denial of service) or limited information disclosure by reading adjacent heap memory contents. Patches are expected from GIMP upstream.
Affected products
- GIMP GIMP <unknown
Timeline
- 2026-08-28: disclosed
- other: CVE-2026-82328 assigned