# CVE-2026-106062: Gimp: gimp: heap buffer overflow in dds loader on crafted directdraw surface file

> An attacker can execute arbitrary code by tricking a user into opening a crafted DDS image file in GIMP due to an integer overflow in buffer size calculations.

- **Severity:** High 7.8 (`CVSS:3.1/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:** 6 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-106062, GHSA-cqfx-pmhf-jmh6, UBUNTU-CVE-2026-106062

## What is CVE-2026-106062?

CVE-2026-106062 is a high-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 DirectDraw Surface (DDS) loader. When loading a crafted DDS image, buffer sizes derived from width, height, and pitch can be computed using 32-bit arithmetic that overflows. The allocated buffer is too small for the amount of pixel data written through GEGL, following integer overflow in size calculations. This may allow heap corruption and, in the worst case, arbitrary code execution in the context of the GIMP process.

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

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


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

Apply the vendor's patch.

## Is CVE-2026-106062 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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