# CVE-2026-66757: Gimp: signed integer overflow in file-sgi (sgi-lib) causes the plugin to crash on rle sgi images

> A signed integer overflow in GIMP's SGI plugin allows attackers to cause a denial of service via crafted RLE-compressed images.

- **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:** 27 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** CLSA-2026-1787057425, CLSA-2026-1787058577, DEBIAN-CVE-2026-66757, GHSA-3xfh-g29g-69hj, UBUNTU-CVE-2026-66757, openSUSE-SU-2026:21733-1, openSUSE-SU-2026:21839-1

## What is CVE-2026-66757?

CVE-2026-66757 is a medium-severity vulnerability in Gimp Gimp, published on 27 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 the file-sgi plugin in GIMP. When processing an RLE-compressed SGI image, the plugin allocates memory for a row table. The image header dimensions (ysize and zsize) are read as 16-bit unsigned integers. If a crafted file sets both dimensions to their maximum value (65535), the multiplication ysize * zsize overflows the standard 32-bit int boundary before being passed to calloc. This integer overflow issue results in undefined behavior, aborting the plugin and causing a denial of service.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gimp` | openSUSE:Leap 16.0 | All versions | 3.0.8-bp160.7.1 |
| `gimp` | openSUSE:Leap 16.0 | All versions | 3.0.8-bp160.8.1 |

Products: Gimp Gimp, Redhat Enterprise Linux.

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

Apply the vendor's patch.

## Is CVE-2026-66757 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-66757 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-66757 and fix it if it is affected.

What it is: CVE-2026-66757 is a medium-severity vulnerability in Gimp Gimp, published on 27 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-66757 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-66757/ (Markdown: https://insights.sbomify.com/CVE-2026-66757/index.md)
```

## Sources

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

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