# CVE-2026-2239: Gimp: gimp: application crash (dos) via crafted psd file due to heap-buffer-overflow

> An attacker can cause a denial of service in GIMP by tricking a user into opening a specially crafted PSD file, triggering a heap-buffer-overflow.

- **Severity:** Low 2.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Mar 2026
- **Updated:** 3 Apr 2026
- **Also known as:** DEBIAN-CVE-2026-2239, GHSA-pjv8-58qr-6mxx, UBUNTU-CVE-2026-2239, openSUSE-SU-2026:10195-1, openSUSE-SU-2026:20275-1

## What is CVE-2026-2239?

CVE-2026-2239 is a low-severity memory corruption vulnerability in Gimp Gimp, published on 26 Mar 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. Heap-buffer-overflow vulnerability exists in the fread_pascal_string function when processing a specially crafted PSD (Photoshop Document) file. This occurs because the buffer allocated for a Pascal string is not properly null-terminated, leading to an out-of-bounds read when strlen() is subsequently called. Successfully exploiting this vulnerability can cause the application to crash, resulting in an application level Denial of Service.

Weakness: CWE-170 (Improper Null Termination)

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

It affects 2 products.


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

Products: Gimp Gimp, Redhat Enterprise Linux.

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

Apply the vendor's patch.

## Is CVE-2026-2239 being exploited?

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

What it is: CVE-2026-2239 is a low-severity memory corruption vulnerability in Gimp Gimp, published on 26 Mar 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-2239 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-2239/ (Markdown: https://insights.sbomify.com/CVE-2026-2239/index.md)
```

## Sources

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

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