CVE-2026-59089: GIMP PlayStation TIM Integer Overflow Denial of Service
GIMP, a widely-used open-source image editor, contains a flaw in its PlayStation TIM image file handler that can crash the application when processing certain malicious image files. The vulnerability stems from incorrect math when the software calculates how much memory to allocate for color data, causing it to misinterpret file contents and ultimately fail. While an attacker cannot steal data or gain system access through this flaw, they can disrupt a user's work by triggering a denial-of-service condition.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 5.5 MEDIUM · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- Weaknesses (CWE)
- CWE-190
- Affected products
- 3 configuration(s)
- Published / Modified
- 2026-07-06 / 2026-07-10
NVD description (verbatim)
A flaw was found in GIMP. The PlayStation TIM loader, responsible for handling PlayStation image files, incorrectly calculates the size of the Color Look-Up Table (CLUT) due to an integer overflow. This occurs when multiplying num_colors and num_cluts, both 16-bit unsigned short integers, resulting in a value exceeding the maximum integer limit. An attacker could exploit this by providing a specially crafted image file, leading to undefined behavior and causing the GIMP plug-in to abort, effectively resulting in a denial of service.
4 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
The PlayStation TIM image loader plug-in in GIMP performs integer overflow arithmetic when calculating CLUT (Color Look-Up Table) buffer size. Specifically, multiplying two 16-bit unsigned integers (num_colors and num_cluts) without bounds checking produces a value that exceeds the maximum representable integer, wrapping around to an incorrect, often much smaller allocation. Subsequent operations on the undersized buffer lead to undefined behavior, typically resulting in a segmentation fault or abort that terminates the plug-in process. This is classified as CWE-190 (Integer Overflow or Wraparound).
Business impact
The availability impact is confined to individual GIMP users or workstations running vulnerable versions. In environments where GIMP is used for batch image processing, automated workflows, or as a service backend, a denial-of-service crash could interrupt production tasks and require manual intervention or service restarts. Collaborative design teams may experience disruptions if a malicious TIM file is shared. However, no data breach, privilege escalation, or system-wide compromise is possible from this vulnerability.
Affected systems
GIMP across its supported versions is affected, as are associated Red Hat Enterprise Linux distributions that package GIMP. The vulnerability manifests only when a user (or automated process) opens a specially crafted PlayStation TIM image file. Systems that do not use GIMP or do not process TIM-format images are unaffected. Desktop users are most at risk; server environments using GIMP are less common but potentially vulnerable if TIM processing is part of the workflow.
Exploitability
This vulnerability requires user interaction: an attacker must trick or socially engineer a user into opening a malicious TIM image file in GIMP. No network exploitation is possible, and local privilege escalation is not supported by the flaw itself. The attack surface is therefore limited to scenarios where untrusted image files are processed. The CVSS vector (AV:L/AC:L/PR:N/UI:R) reflects this: local attack vector, low complexity, no privilege needed, but user interaction required. The flaw is not trivial to exploit but is straightforward once a target is identified and a crafted file is delivered.
Remediation
Users and administrators should apply security updates when GIMP releases a patched version that corrects the integer overflow in the PlayStation TIM loader. Verify against the official GIMP project advisory and Red Hat Enterprise Linux security bulletins for specific version numbers and availability. As an interim measure, users can mitigate risk by avoiding the opening of TIM image files from untrusted sources and disabling or removing the TIM loader plug-in if not required for regular workflows.
Patch guidance
Check the GIMP project's official website and Red Hat security advisories for the next available maintenance release that includes a fix for CVE-2026-59089. Apply patches promptly to affected systems. For Red Hat Enterprise Linux users, verify whether an errata has been published and schedule updates according to your change management and availability windows. Test any patch in a development environment first to confirm compatibility with existing workflows and other plug-ins.
Detection guidance
Monitor for crashes or unexpected terminations of GIMP processes, particularly if they occur after opening image files from unknown sources. Intrusion detection systems focused on file integrity can flag attempts to introduce suspicious TIM files into trusted locations. Logging of GIMP plug-in errors or segmentation faults may reveal exploitation attempts. However, because this is a client-side denial of service and not a network-based attack, traditional perimeter detection is limited; endpoint monitoring and user reports are more effective.
Why prioritize this
This vulnerability receives a MEDIUM severity rating due to its denial-of-service impact (CWE-190 in image parsing context) and requirement for user interaction. While the practical risk is lower than a remote code execution flaw, it should still be addressed promptly in environments where GIMP is integral to workflows or where image processing is automated. Prioritize patching in organizations that heavily rely on GIMP or that regularly process images from external or untrusted sources. For general desktop users and most enterprise environments where GIMP is optional, patch within standard quarterly or bi-monthly cycles.
Risk score, explained
The CVSS 3.1 score of 5.5 (MEDIUM) reflects: local-only attack vector (typical for file-based exploits), low attack complexity (the integer overflow is straightforward to trigger with a crafted file), no privilege requirement, but mandatory user interaction (user must open the file). The impact assessment grants no confidentiality or integrity damage but assigns high availability impact (application crash). This score appropriately captures that the threat is real and should be remediated, but poses lower risk than network-exploitable or privilege-escalation flaws.
Frequently asked questions
Can an attacker remotely exploit this flaw to compromise my system?
No. The vulnerability requires local access and user interaction; specifically, a user must open a malicious TIM image file in GIMP. There is no remote attack vector, and successful exploitation only causes the GIMP process to crash, not system compromise or data theft.
I don't use GIMP or TIM image files. Am I affected?
No. If you do not have GIMP installed or do not work with PlayStation TIM format images, this vulnerability does not impact you. Users of other image editors (Photoshop, Affinity, etc.) are not affected unless they also use GIMP.
What should I do if a GIMP patch is not yet available?
Until a patch is released, avoid opening TIM image files from untrusted or unknown sources. If TIM file handling is not essential for your work, consider disabling the PlayStation TIM loader plug-in in GIMP's preferences. Monitor official GIMP and Red Hat security channels for patch availability.
Will this vulnerability be exploited in the wild?
The vulnerability is not currently tracked in the CISA Known Exploited Vulnerabilities (KEV) catalog, indicating no known active exploitation as of the publication date. However, the ease of crafting a malicious TIM file means weaponization is possible; do not rely on low real-world exploitation as justification to delay patching indefinitely.
This analysis is based on the CVE description and CVSS vector published as of 2026-07-10. Specific patch version numbers and detailed remediation steps must be verified against official GIMP project advisories, Red Hat security bulletins, and vendor security statements. SEC.co does not provide real-time threat intelligence on active exploitation. Organizations should consult their vulnerability management and incident response teams for guidance tailored to their environment, risk tolerance, and business criticality. No exploit code or proof-of-concept is provided or should be inferred from this document. Source: NVD (public-domain), retrieved 2026-08-15. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-58384HIGHGIMP PSD Parser Integer Overflow – Heap Corruption Risk
- CVE-2026-57965MEDIUMInteger Overflow in spice-vdagent Causes Denial of Service
- CVE-2026-58380HIGHGIMP PNM Parser Stack Buffer Overflow – Off-by-One Memory Corruption
- CVE-2025-55647MEDIUMGPAC MP4Box 2.4 Out-of-Memory Denial of Service Vulnerability
- CVE-2026-0039MEDIUMAndroid Integer Overflow Denial of Service Vulnerability
- CVE-2026-0040MEDIUMAndroid ubsan_throwing_runtime Integer Overflow DoS Vulnerability
- CVE-2026-0041MEDIUMAndroid UBSan Integer Overflow Remote Denial of Service
- CVE-2026-0043MEDIUMAndroid UBSan Integer Overflow Local Privilege Escalation