# CVE-2026-58379: Gimp: gimp: heap buffer overflow in read_channel_data()

> A heap buffer overflow in GIMP's PSP parser allows remote attackers to execute arbitrary code or cause denial of service via crafted images.

- **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:** 3 Jul 2026
- **Updated:** 12 Oct 2026
- **Also known as:** ALSA-2026:38496, CLSA-2026-1784134559, CLSA-2026-1784136022, DEBIAN-CVE-2026-58379, GHSA-rx3j-28q8-xw3m, RHSA-2026:38496, UBUNTU-CVE-2026-58379

## What is CVE-2026-58379?

CVE-2026-58379 is a high-severity memory corruption vulnerability in Gimp Gimp, published on 3 Jul 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 GIMP's Paint Shop Pro (PSP) file format parser. This heap buffer overflow vulnerability allows a remote attacker to cause arbitrary code execution or a denial of service (DoS) by tricking a user into opening a specially crafted PSP image file. The vulnerability occurs because the software incorrectly calculates buffer sizes when processing low bit-depth images, leading to an overwrite of adjacent memory.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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

It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gimp` | AlmaLinux:9 | All versions | 2:3.0.4-4.el9_8.5 |
| `gimp-libs` | AlmaLinux:9 | All versions | 2:3.0.4-4.el9_8.5 |
| `gimp` | Red Hat:enterprise_linux:9::appstream | All versions | 2:3.0.4-4.el9_8.5 |
| `gimp-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 2:3.0.4-4.el9_8.5 |
| `gimp-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 2:3.0.4-4.el9_8.5 |
| `gimp-devel-tools-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 2:3.0.4-4.el9_8.5 |
| `gimp-libs` | Red Hat:enterprise_linux:9::appstream | All versions | 2:3.0.4-4.el9_8.5 |
| `gimp-libs-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 2:3.0.4-4.el9_8.5 |

Products: Gimp Gimp, Redhat Enterprise Linux, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Update Services for Sap Solutions.

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

Apply the vendor's patch.

## Is CVE-2026-58379 being exploited?

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

## 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-58379 and fix it if it is affected.

What it is: CVE-2026-58379 is a high-severity memory corruption vulnerability in Gimp Gimp, published on 3 Jul 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-58379 in the wild and no public exploit code.

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

## Sources

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

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