CVE-2026-59087: Gimp: heap buffer overflow in `file-seattle-filmworks` load — `fread` writes attacker-controlled length into undersized allocation
A flaw was found in the GIMP image manipulation program, specifically within its Seattle Filmworks file loader. A remote attacker could exploit this vulnerability by tricking a user into opening a specially crafted Seattle Filmworks file. This could lead to a heap overflow, allowing the attacker to write several kilobytes of controlled data beyond the intended memory buffer. Such an overflow can result in memory corruption, potentially leading to arbitrary code execution or a denial of service.
Other sources
The Seattle Filmworks file loader reads two file-position-derived values, index and metadatalen[1], uses only metadatalen[1] to size the allocation for photodate, then freads index - metadatalen[1] bytes into it. Both values are attacker-controlled and independent. When index ≫ metadatalen[1], the read overflows the heap by up to several KB of attacker-controlled bytes. In a build with FORTIFYSOURCE (Ubuntu default), glibc detects this at runtime and aborts. In a non-FORTIFY build the corruption is silent.
Issue Link: https://gitlab.gnome.org/GNOME/gimp/-/workitems/16491
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-59087?
CVE-2026-59087 has a severity rating of high with a score of 7.8.
How do I fix CVE-2026-59087?
To fix CVE-2026-59087, update GIMP to the latest version that addresses this vulnerability.
What type of vulnerability is CVE-2026-59087?
CVE-2026-59087 is a heap buffer overflow vulnerability in the file-seattle-filmworks loader of GIMP.
Who can exploit CVE-2026-59087?
CVE-2026-59087 can be exploited by a remote attacker by tricking a user into opening a specially crafted Seattle Filmworks file.
What are the potential impacts of CVE-2026-59087?
The potential impacts of CVE-2026-59087 include arbitrary code execution due to heap overflow, which can compromise system integrity.