Quick answers
- Is CVE-2026-18305 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-18305 being exploited in the wild.
- How severe is CVE-2026-18305?
- High severity, with a CVSS score of 7.8, published 20 August 2026.
- Which products and versions are affected?
- GNOME GIMP <UNKNOWN>.
- Is there a fix for CVE-2026-18305?
- A patch was published on 2026-07-29: Patch released; fix available at gitlab.gnome.org/GNOME/gimp/-/commit/0a45a2b51b877829ef523131b50c0eb2a933b8a1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-18305 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-18305?
- 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
This vulnerability is an integer overflow in GIMP's TIF (Tagged Image File) parsing routine. The flaw stems from insufficient validation of user-supplied data in TIF file headers, allowing an integer overflow during buffer allocation. When a victim opens a maliciously crafted TIF file, the overflow is triggered before memory is allocated for image data, enabling an attacker to write arbitrary code to memory. Exploitation requires user interaction (opening a malicious file) but does not require authentication or elevated privileges. GIMP has issued a patch available on their GitLab repository.
Affected products
- GNOME GIMP <UNKNOWN>
Timeline
- 2026-04-17: disclosed: Vulnerability reported to vendor
- 2026-07-29: patched: Patch released; fix available at gitlab.gnome.org/GNOME/gimp/-/commit/0a45a2b51b877829ef523131b50c0eb2a933b8a1
- 2026-07-29: advisory: Coordinated public release of advisory ZDI-26-458