# CVE-2026-2272: Gimp: gimp: memory corruption due to integer overflow in ico file handling

> A remote attacker can cause a denial of service in GIMP by providing a specially crafted ICO file that triggers an integer overflow and memory corruption.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Mar 2026
- **Updated:** 3 Apr 2026
- **Also known as:** DEBIAN-CVE-2026-2272, GHSA-8g7q-m2xj-67ch, UBUNTU-CVE-2026-2272

## What is CVE-2026-2272?

CVE-2026-2272 is a medium-severity vulnerability in Gimp Gimp, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A flaw was found in GIMP. An integer overflow vulnerability exists when processing ICO image files, specifically in the `ico_read_info` and `ico_read_icon` functions. This issue arises because a size calculation for image buffers can wrap around due to a 32-bit integer evaluation, allowing oversized image headers to bypass security checks. A remote attacker could exploit this by providing a specially crafted ICO file, leading to a buffer overflow and memory corruption, which may result in an application level denial of service.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 2 products.


Products: Gimp Gimp, Redhat Enterprise Linux.

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

Apply the vendor's patch.

## Is CVE-2026-2272 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2272 exists.

## Other vulnerabilities in Gimp Gimp

- [CVE-2010-4541](https://insights.sbomify.com/CVE-2010-4541/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-3909](https://insights.sbomify.com/CVE-2009-3909/): Integer overflow in n/a (critical 9.3)
- [CVE-2009-1570](https://insights.sbomify.com/CVE-2009-1570/): Integer overflow in n/a (critical 9.3)
- [CVE-2009-0723](https://insights.sbomify.com/CVE-2009-0723/): Integer overflow in n/a (critical 9.3)
- [CVE-2009-0733](https://insights.sbomify.com/CVE-2009-0733/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2272 is a medium-severity vulnerability in Gimp Gimp, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2272 exists.

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

## Sources

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

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