CVE-2026-18308: GIMP integer overflow in TIF file parsing

CVE-2026-18308 · Severity: high · CVSS 7.8 · Published 2026-08-20

GIMP is a widely-used image editing tool. A flaw in how GIMP processes TIF (Tagged Image File Format) image files allows attackers to craft malicious image files that trigger an integer overflow, enabling arbitrary code execution. An attacker would trick users into opening a malicious image file, potentially compromising the user's system and granting full access to their data and applications.

Technologies: Gimp. Vendors: Gimp.

Quick answers

Is CVE-2026-18308 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-18308 being exploited in the wild.
How severe is CVE-2026-18308?
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-18308?
A patch was published on 2026-07-29: Patch made available; coordinated public disclosure Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-18308 attacked?
It is attacked with local access.
Am I affected by CVE-2026-18308?
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 integer overflow vulnerability exists in GIMP's TIF file parser due to insufficient validation of user-supplied data before buffer allocation. When parsing specially crafted TIF files, an integer overflow can occur during size calculations, leading to undersized buffer allocation. This allows an attacker to write beyond the allocated buffer, achieving arbitrary code execution in the context of the GIMP process. The attack requires user interaction (opening a malicious TIF file) but does not require elevated privileges. A patch is available from the GIMP project repository.

Affected products

  • GIMP GIMP

Timeline

  • 2026-04-17: disclosed: Vulnerability reported to vendor
  • 2026-07-29: patched: Patch made available; coordinated public disclosure
  • 2026-07-29: advisory: ZDI-26-461 advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.