# CVE-2026-106061: Gimp: gimp: heap buffer over-read in x cursor (xmc) thumbnail loader on crafted file

> An attacker can cause a crash or memory corruption in GIMP by providing a crafted X cursor file that triggers an integer overflow in thumbnail generation.

- **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:** 7 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-106061, GHSA-p76v-2jpq-7gvc, UBUNTU-CVE-2026-106061

## What is CVE-2026-106061?

CVE-2026-106061 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 7 Oct 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’s X cursor (XMC) thumbnail loader. When GIMP generates a thumbnail for a crafted XMC file, it allocates a pixel buffer using a width * height size computed in 32-bit signed arithmetic. If that product overflows, the allocation is smaller than the true image extent. A subsequent GEGL buffer read uses the unwrapped dimensions and performs an out-of-bounds read on the heap, after integer overflow in the size calculation. This can crash GIMP or corrupt process memory.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Apply the vendor's patch.

## Is CVE-2026-106061 being exploited?

There is no known exploitation of CVE-2026-106061 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-106061 and fix it if it is affected.

What it is: CVE-2026-106061 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 7 Oct 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-106061 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. 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-106061/ (Markdown: https://insights.sbomify.com/CVE-2026-106061/index.md)
```

## Sources

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

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