# CVE-2026-92248: Gimp: integer overflow when generating a thumbnail preview for a psd file

> An integer overflow in GIMP's PSD plugin allows attackers to execute arbitrary code or crash the application via a crafted image file.

- **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:** 15 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-92248, GHSA-v7fc-wcg3-84gx, UBUNTU-CVE-2026-92248

## What is CVE-2026-92248?

CVE-2026-92248 is a high-severity vulnerability in GNOME GIMP, published on 15 Sep 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 the file-psd plugin in GIMP. When generating a thumbnail preview for a specially crafted PSD (Photoshop Document) image file, an integer overflow occurs during the multiplication of values from an embedded JPEG header. This leads to an undersized heap allocation, resulting in a heap-based buffer overflow when the image data is decoded. This buffer overflow corrupts adjacent heap objects, allowing for a controlled memory write that can result in an application crash or arbitrary code execution.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

Apply the vendor's patch.

## Is CVE-2026-92248 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92248 is a high-severity vulnerability in GNOME GIMP, published on 15 Sep 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-92248 in the wild and no public exploit code.

Affected product: GNOME 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-92248/ (Markdown: https://insights.sbomify.com/CVE-2026-92248/index.md)
```

## Sources

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

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