# CVE-2026-4887: Gimp: gimp:memory disclosure and denial of service via specially crafted pcx image

> A heap buffer over-read in GIMP's PCX loader allows attackers to disclose memory or crash the application via a crafted image.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/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:** 26 Mar 2026
- **Updated:** 16 Jun 2026
- **Also known as:** CLSA-2026-1777397602, DEBIAN-CVE-2026-4887, GHSA-wmqx-rmqw-vxp8, OESA-2026-1810, OESA-2026-1811, OESA-2026-1812, OESA-2026-1813, SUSE-SU-2026:2756-1, UBUNTU-CVE-2026-4887

## What is CVE-2026-4887?

CVE-2026-4887 is a medium-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. This issue is a heap buffer over-read in GIMP PCX file loader due to an off-by-one error. A remote attacker could exploit this by convincing a user to open a specially crafted PCX image. Successful exploitation could lead to out-of-bounds memory disclosure and a possible application crash, resulting in a Denial of Service (DoS).

Weakness: CWE-193 (Off-by-one Error)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gimp` | SUSE:Linux Enterprise Module for Package Hub 15 SP7 | All versions | 2.10.30-150400.3.53.1 |
| `gimp` | SUSE:Linux Enterprise Workstation Extension 15 SP7 | All versions | 2.10.30-150400.3.53.1 |

Products: Gimp Gimp.

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

Apply the vendor's patch.

## Is CVE-2026-4887 being exploited?

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

What it is: CVE-2026-4887 is a medium-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-4887 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-4887/ (Markdown: https://insights.sbomify.com/CVE-2026-4887/index.md)
```

## Sources

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

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