GIMP CVE-2026-18303

The victim must actively open a malicious TIF file in GIMP - for example, by downloading and opening an image from a malicious webpage, or opening an attachment. No authentication to any service is required from the attacker's perspective (PR:N in CVSS). Exploitation is limited to GIMP 3.2.2 (and potentially adjacent 3.x versions); the attack vector is local execution (AV:L), meaning network reachability to GIMP is not required - the attacker must rely on social engineering to induce the file-open action. Impact is scoped to the current user process (S:U), so privilege escalation beyond the victim's OS account is not inherent to this vulnerability.

The CVSS 3.0 base score of 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects high confidentiality, integrity, and availability impact with low attack complexity, but the local attack vector (AV:L) and required user interaction (UI:R) constrain realistic risk. The 'remote attackers' framing in the description refers to remote delivery of the malicious file rather than network-reachable exploitation without user action - the attack executes locally when the victim opens the file. No EPSS data was provided in the intelligence feed, so exploitation probability cannot be quantified. This CVE is not listed in the CISA KEV catalog, and no public POC has been identified at time of analysis. The real-world priority is moderate: GIMP is widely used in creative and Linux-centric environments, the user-interaction barrier lowers practical risk compared to a network-exploitable flaw, but successful exploitation yields full code execution. Organizations with GIMP deployed on endpoints handling untrusted image files should treat this with meaningful urgency.

An attacker crafts a malicious TIFF image containing a deliberately oversized field that triggers the stack buffer overflow in GIMP's TIF parser, then hosts it on a compromised webpage or delivers it as an email attachment. When a victim opens the file in GIMP 3.2.2, the overflow corrupts the call stack, redirecting execution to attacker-controlled shellcode or a ROP chain, achieving code execution with the victim user's full privileges on the local system. No public POC has been identified at time of analysis, but the ZDI advisory publication typically precedes coordinated public disclosure.