Quick answers
- Is CVE-2026-18304 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-18304 being exploited in the wild.
- How severe is CVE-2026-18304?
- High severity, with a CVSS score of 7.8, published 20 August 2026.
- Which products and versions are affected?
- Gimp prior to patch (commit ad32d22c347674fa1bb5b60935c376b673d946e7).
- Is there a fix for CVE-2026-18304?
- A patch was published on 2026-07-29: GIMP patch available Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-18304 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-18304?
- 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 vulnerability is an integer overflow in GIMP's TIF file parser that occurs before buffer allocation. Insufficient validation of user-supplied data in TIFF files allows an attacker to trigger an integer overflow, leading to allocation of an undersized buffer. When subsequent operations write to this buffer, a heap overflow occurs, enabling arbitrary code execution. The attack requires user interaction (opening a malicious TIFF file), but is otherwise remote/local depending on delivery vector. GIMP has released a patch available at the GitLab commit referenced in the advisory.
Affected products
- GIMP GIMP prior to patch (commit ad32d22c347674fa1bb5b60935c376b673d946e7)
Timeline
- 2026-04-17: disclosed: Vulnerability reported to vendor
- 2026-07-29: advisory: Coordinated public release of advisory (ZDI-26-457)
- 2026-07-29: patched: GIMP patch available