Quick answers
- Is CVE-2026-18301 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-18301 being exploited in the wild.
- How severe is CVE-2026-18301?
- 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-18301?
- A patch was published on 2026-07-29: Patch released via merge request Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-18301 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-18301?
- 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
An integer overflow vulnerability exists in GIMP's PSD file parsing, specifically in the `read_channel_data` function. The flaw stems from insufficient validation of user-supplied data when allocating buffers for channel data, allowing an attacker to trigger an integer overflow before buffer allocation. The attack requires user interaction—the victim must open a malicious PSD file. An attacker can leverage this to execute arbitrary code in the context of the GIMP process. GIMP has released a patch that increases vulnerable variables from guint32 to gsize and adds graceful failure handling for memory allocation errors.
Affected products
- GIMP GIMP
Timeline
- 2026-04-17: disclosed: Vulnerability reported to vendor
- 2026-07-29: patched: Patch released via merge request
- 2026-07-29: advisory: Coordinated public release of advisory