# CVE-2026-42169: Gimp: gimp apng loader heap-buffer-overflow when fctl width exceeds ihdr width (file-png.c)

> Attackers can execute arbitrary code by tricking users into opening specially crafted APNG or DDS image files in GIMP.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Aug 2026
- **Updated:** 12 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-42169, GHSA-xq2c-w9r3-rwr6, OESA-2026-3413, OESA-2026-3414, UBUNTU-CVE-2026-42169

## What is CVE-2026-42169?

CVE-2026-42169 is a high-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 4 Aug 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-buffer-overflow vulnerability exists in the APNG (Animated PNG) file loader of GIMP. This flaw occurs when the `fcTL` width exceeds the `IHDR` width, leading to pixel data being written past the end of a heap allocation. Additionally, a heap-based buffer overflow exists in the DDS plug-in due to a BPP mismatch in the `load_layer()` function. Both vulnerabilities can be triggered by opening a specially crafted image file, potentially leading to code execution.

Weakness: CWE-131 (Incorrect Calculation of Buffer Size)

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

It affects 2 products.


Products: Redhat Enterprise Linux, Redhat Enterprise Linux Eus.

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

Apply the vendor's patch.

## Is CVE-2026-42169 being exploited?

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

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2018-14667](https://insights.sbomify.com/CVE-2018-14667/): Red Hat JBoss RichFaces Framework Expression Language Injection (critical 9.8, exploited in the wild)
- [CVE-2021-20325](https://insights.sbomify.com/CVE-2021-20325/): Missing fixes for CVE-2021-40438 and CVE-2021-26691 in the versions of httpd, as shipped in Red Hat Enterprise Linux 8.5.0, causes a securit (critical 9.8)
- [CVE-2018-25011](https://insights.sbomify.com/CVE-2018-25011/): Memory corruption in libwebp (critical 9.8)
- [CVE-2018-25014](https://insights.sbomify.com/CVE-2018-25014/): Other in libwebp (critical 9.8)
- [CVE-2014-3585](https://insights.sbomify.com/CVE-2014-3585/): Supply chain in redhat-upgrade-tool (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42169 is a high-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 4 Aug 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-42169 in the wild and no public exploit code.

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

## Sources

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

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