Quick answers
- Is CVE-2026-18303 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-18303 being exploited in the wild.
- How severe is CVE-2026-18303?
- 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-18303?
- A patch was published on 2026-07-29: GIMP patch released; see https://gitlab.gnome.org/GNOME/gimp/-/commit/5633b362026c6e5b2beb559a10cd76fa32a47592 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-18303 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-18303?
- 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
A stack-based buffer overflow vulnerability exists in GIMP's TIF file parser due to insufficient validation of user-supplied data length before copying to a stack buffer. The vulnerability is reachable when a user opens a crafted TIF file, either by visiting a malicious web page or directly opening a malicious file. Successful exploitation allows an attacker to execute arbitrary code in the context of the GIMP process with the privileges of the user running GIMP. GIMP has released a patch to address this issue. No active exploitation in the wild has been reported.
Affected products
- GIMP GIMP
Timeline
- 2026-04-17: disclosed: Vulnerability reported to vendor
- 2026-07-29: advisory: Coordinated public release of advisory (ZDI-26-456)
- 2026-07-29: patched: GIMP patch released; see https://gitlab.gnome.org/GNOME/gimp/-/commit/5633b362026c6e5b2beb559a10cd76fa32a47592