Quick answers
- Is CVE-2026-18307 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-18307 being exploited in the wild.
- How severe is CVE-2026-18307?
- High severity, with a CVSS score of 7.8, published 20 August 2026.
- Which products and versions are affected?
- GIMP GIMP.
- Is there a fix for CVE-2026-18307?
- A patch was published on 2026-07-29: GIMP issued an update; patch available via GitLab commit bace3e7fd54104fe6b70c1703e9b982a4770811d Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-18307 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-18307?
- Check whether you run Gimp. 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 a classic heap-based buffer overflow in GIMP's TIF file parsing code. The root cause is insufficient validation of user-supplied data length before copying it to a heap-allocated buffer. An attacker can craft a malicious TIF file with oversized data fields to trigger the overflow. Attack vector is local/user interaction: the target must open the malicious TIF file. An authenticated attacker or external attacker can exploit this to execute arbitrary code in the context of GIMP's process. A patch has been released by GIMP; details are available in the referenced GitLab commit.
Affected products
- GIMP GIMP
Timeline
- 2026-04-17: disclosed: Vulnerability reported to vendor
- 2026-07-29: advisory: Coordinated public release of advisory
- 2026-07-29: patched: GIMP issued an update; patch available via GitLab commit bace3e7fd54104fe6b70c1703e9b982a4770811d