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

> An attacker can trigger a heap buffer overflow in GIMP's GIF 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:** No
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-106064, GHSA-v6pf-7x6j-gpfr, UBUNTU-CVE-2026-106064

## What is CVE-2026-106064?

CVE-2026-106064 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 heap-based buffer overflow was found in GIMP’s GIF export plug-in. Exporting an image with very large width and height can cause 32-bit overflow when computing the pixel buffer size. The plug-in allocates a buffer based on the wrapped value while GEGL writes using the true image extent, rooted in integer overflow

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

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


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

No fix has been published for CVE-2026-106064 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-106064 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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