# CVE-2026-59089: Gimp: gimp: denial of service via integer overflow in playstation tim loader

> An attacker can cause a denial of service in GIMP by providing a specially crafted PlayStation TIM image file that triggers an integer overflow.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Jul 2026
- **Updated:** 21 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-59089, GHSA-7v2w-74r7-8rq2, UBUNTU-CVE-2026-59089

## What is CVE-2026-59089?

CVE-2026-59089 is a medium-severity vulnerability in Gimp Gimp, published on 6 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2026-59089?

It affects 2 products.


Products: Gimp Gimp, Redhat Enterprise Linux.

## How do I fix CVE-2026-59089?

Apply the vendor's patch.

## Is CVE-2026-59089 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59089 exists.

## Other vulnerabilities in Gimp Gimp

- [CVE-2010-4541](https://insights.sbomify.com/CVE-2010-4541/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-3909](https://insights.sbomify.com/CVE-2009-3909/): Integer overflow in n/a (critical 9.3)
- [CVE-2009-1570](https://insights.sbomify.com/CVE-2009-1570/): Integer overflow in n/a (critical 9.3)
- [CVE-2009-0723](https://insights.sbomify.com/CVE-2009-0723/): Integer overflow in n/a (critical 9.3)
- [CVE-2009-0733](https://insights.sbomify.com/CVE-2009-0733/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59089 and fix it if it is affected.

What it is: CVE-2026-59089 is a medium-severity vulnerability in Gimp Gimp, published on 6 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59089 exists.

Affected product: Gimp Gimp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59089/ (Markdown: https://insights.sbomify.com/CVE-2026-59089/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59089
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59089
- OSV: https://osv.dev/vulnerability/CVE-2026-59089

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59089/
Summaries are generated and may contain mistakes; the official description above is the record.