# CVE-2026-78465: Gimp: integer overflow in pcx loader (planes=4) leads to heap overflow on 32-bit

> A crafted PCX file triggers an integer overflow in GIMP's 32-bit plugin, causing a heap overflow that allows arbitrary code execution or denial of service.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/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:** 24 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-78465, GHSA-944m-78f8-q7cr, UBUNTU-CVE-2026-78465

## What is CVE-2026-78465?

CVE-2026-78465 is a high-severity vulnerability in Gimp Gimp, published on 24 Aug 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-pcx plugin in GIMP, affecting 32-bit builds only. When processing a PCX image file, the plugin calculates memory allocation sizes based on the image dimensions and the number of color planes. If a crafted file sets the number of planes to 4 alongside sufficiently large dimensions, the calculation exceeds the 32-bit integer limit and overflows, resulting in an undersized heap-based buffer allocation. This integer overflow issue results in a heap-based buffer overflow when the plugin subsequently writes image data into the undersized 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-78465?

It affects 1 product.


Products: Gimp Gimp.

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

Apply the vendor's patch.

## Is CVE-2026-78465 being exploited?

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

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

## Sources

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

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