# CVE-2026-106063: Gimp: gimp: heap buffer overflow in dicom export on oversized image dimensions

> An attacker can trigger a heap buffer overflow in GIMP's DICOM export by providing oversized image dimensions, potentially leading to code execution or application crash.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/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:** 6 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-106063, GHSA-j336-2pgh-rf7p, UBUNTU-CVE-2026-106063

## What is CVE-2026-106063?

CVE-2026-106063 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 6 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 heap-based buffer overflow was found in GIMP’s DICOM export plug-in. When exporting an image with extremely large width and height, the export path allocates a buffer using a 32-bit width * height (and bytes-per-pixel) product that can overflow. GEGL then writes the full uncompressed extent into the undersized buffer, after integer overflow in the allocation size

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

Apply the vendor's patch.

## Is CVE-2026-106063 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-106063 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 6 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-106063 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-106063/ (Markdown: https://insights.sbomify.com/CVE-2026-106063/index.md)
```

## Sources

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

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