CVE-2026-59089 gimp vulnerability
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.
Quick answer
gimp should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- 3.2.6
- 8.0
- 9.0
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
GIMP is affected by CVE-2026-59089, a integer overflow risk. A flaw was found in GIMP. The recommended remediation is to update to a GIMP package or distribution update containing the vendor fix for CVE-2026-59089, or the latest vendor-supported fixed GIMP release when available. Until the update is complete, avoid opening untrusted PlayStation TIM image files and isolate image processing until patched, review logs, and reduce exposure of the affected service, firmware path, or build workflow.
- Inventory every deployment, package, firmware image, appliance, device family, container, build runner, or service that uses GIMP.
- Confirm the installed version or firmware build and compare it with listed affected versions include 3.2.6, 8.0, 9.0 and the source advisory for CVE-2026-59089.
- Apply the vendor-supported fix: update to a GIMP package or distribution update containing the vendor fix for CVE-2026-59089, or the latest vendor-supported fixed GIMP release when available.
- If the update cannot be applied immediately, avoid opening untrusted PlayStation TIM image files and isolate image processing until patched; disable unnecessary public access, endpoints, uploads, build inputs, hardware features, or high-risk integrations until patched.
- Review application, device, kernel, firmware, build, package manager, container, authentication, and audit logs for activity related to CVE-2026-59089.
- Rotate sessions, API tokens, service credentials, signing keys, integration keys, and administrator passwords if logs or affected data indicate compromise, code execution, credential exposure, or unauthorized access.
- Clear caches, restart affected services, rebuild affected containers or firmware images when appropriate, and remove temporary files, generated artifacts, stored payloads, or unsafe configuration created during exploitation attempts.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm GIMP now reports a GIMP package or distribution update containing the vendor fix for CVE-2026-59089, or the latest vendor-supported fixed GIMP release when available or a later vendor-supported fixed release/build for the deployed branch or device family.
- Verify the affected workflow no longer allows the behavior described in CVE-2026-59089, using a safe regression test, vendor validation method, or firmware/package inventory check.
- Review logs after remediation for continued exploit attempts, denial-of-service symptoms, suspicious redirects, unauthorized requests, file access, memory corruption symptoms, or configuration changes.
- Rerun a Fixnx scan and any product-specific scanner, package audit, firmware inventory, device health check, or manual regression test relevant to the affected service.
- Document affected assets, fixed versions, mitigation decisions, validation evidence, and any cleanup, rebuild, or credential rotation performed.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-59089?
gimp versions listed as affected should be reviewed: 3.2.6, 8.0, 9.0.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.