Quick answers
- Is CVE-2026-18300 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-18300 being exploited in the wild.
- How severe is CVE-2026-18300?
- 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-18300?
- A patch was published on 2026-07-29: GIMP issued an update; coordinated public release of advisory Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-18300 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-18300?
- 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 an integer overflow in GIMP's HDR file parsing logic, specifically in how the application validates and processes user-supplied data before allocating buffers. The flaw exists in the parsing of HDR files and results from insufficient validation of input data, leading to an integer overflow that can cause a buffer to be allocated with an incorrect size. The attack vector is local with user interaction required—a target must open a malicious HDR file. An attacker can exploit this to execute arbitrary code in the context of GIMP's process. GIMP has released a patch addressing this issue, as documented in the upstream GEGL repository commit.
Affected products
- GIMP GIMP
Timeline
- 2026-04-17: disclosed: Vulnerability reported to vendor
- 2026-07-29: patched: GIMP issued an update; coordinated public release of advisory
- 2026-07-29: advisory: ZDI-26-453 advisory published