# CVE-2026-2045: GIMP XWD File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability

> Remote attackers can execute arbitrary code by tricking users into opening malicious XWD files in GIMP due to an out-of-bounds write flaw.

- **Severity:** High 7.8 (`CVSS:3.0/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:** 20 Feb 2026
- **Updated:** 15 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-2045, GHSA-wx92-h8q5-hfm6, UBUNTU-CVE-2026-2045

## What is CVE-2026-2045?

CVE-2026-2045 is a high-severity memory corruption vulnerability in Gimp Gimp, published on 20 Feb 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

GIMP XWD File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GIMP. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

The specific flaw exists within the parsing of XWD files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-28265.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Gimp Gimp.

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

Apply the vendor's patch.

## Is CVE-2026-2045 being exploited?

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

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

## Sources

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

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