# CVE-2026-40915: Gimp: gimp: heap buffer overflow due to integer overflow in fits image loader

> A remote attacker can cause a heap buffer overflow and potential code execution in GIMP by providing a specially crafted FITS image file.

- **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:** 15 Apr 2026
- **Updated:** 28 Apr 2026
- **Also known as:** DEBIAN-CVE-2026-40915, GHSA-4f9g-vrx9-f8cq, UBUNTU-CVE-2026-40915

## What is CVE-2026-40915?

CVE-2026-40915 is a medium-severity vulnerability in Gimp Gimp, published on 15 Apr 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. A remote attacker could exploit an integer overflow vulnerability in the FITS image loader by providing a specially crafted FITS file. This integer overflow leads to a zero-byte memory allocation, which is then subjected to a heap buffer overflow when processing pixel data. Successful exploitation could result in a denial of service (DoS) or potentially arbitrary code execution.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 2 products.


Products: Gimp Gimp, Redhat Enterprise Linux.

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

Apply the vendor's patch.

## Is CVE-2026-40915 being exploited?

There is no known exploitation of CVE-2026-40915 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-40915 and fix it if it is affected.

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

## Sources

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

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