# CVE-2026-66758: Gimp: integer overflow in file-fits plugin causes a heap-based buffer overflow on crafted fits images

> An integer overflow in GIMP's FITS plugin allows attackers to trigger a heap buffer overflow via crafted images, potentially leading to code execution or crashes.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:** 12 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-66758, GHSA-p2xc-g3qc-p2mq, UBUNTU-CVE-2026-66758

## What is CVE-2026-66758?

CVE-2026-66758 is a high-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-fits plugin in GIMP. When processing a FITS image file, the plugin calculates memory allocation sizes using signed 32-bit integers for width and height. If a crafted file sets both values to large values, their product exceeds 2^31 and overflows, resulting in an undersized heap-based buffer allocation. This integer overflow issue results in a heap-based buffer overflow when cfitsio subsequently writes a full row of pixels in the buffer, causing memory corruption, potentially leading to arbitrary code execution or a denial of service.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 2 products.


Products: Gimp Gimp, Redhat Enterprise Linux.

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

Apply the vendor's patch.

## Is CVE-2026-66758 being exploited?

There is no known exploitation of CVE-2026-66758 in the wild and no public exploit code.

## 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-66758 and fix it if it is affected.

What it is: CVE-2026-66758 is a high-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: There is no known exploitation of CVE-2026-66758 in the wild and no public exploit code.

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-66758/ (Markdown: https://insights.sbomify.com/CVE-2026-66758/index.md)
```

## Sources

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

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