CVE-2026-58380: GIMP PNM Parser Buffer Overflow

Who is Affected?

The affected product is GIMP. The vulnerable component is the PNM parser, and the vulnerable function identified in the primary sources is pnmscanner_gettoken(). Based on the available upstream issue metadata, the bug was reproduced on GIMP 3.2.1. That is the only specific affected version that can be directly quoted from the retrieved source material without overclaiming.

What is not currently confirmed from the retrieved primary sources is the full affected version range or the first fixed release number. The research note explicitly indicates that the full upstream issue body and commit details were not fully exposed in the retrieved text. So the most accurate statement is: GIMP 3.2.1 is confirmed affected, and an upstream fix exists in commit 83699817, but the exact broader affected range and fixed release number were not verifiably available from the consulted sources. In the absence of full version data, defenders should assume any deployed GIMP build near or including 3.2.1 may require review against vendor package changelogs or the upstream patch.

Why This Vulnerability Matters Operationally

Image parsers routinely process attacker-controlled content from email attachments, downloads, chat transfers, ticket uploads, and shared storage. Even when the attack requires user interaction, malformed file parsing bugs are valuable to attackers because they target software that many users trust and open routinely. A malicious PNM file could be delivered under the guise of test assets, design files, or content conversion workflows.

For IT and security teams, the main operational question is not whether this bug is internet-facing in the classic remote-service sense, but whether users, artists, designers, or automation systems process untrusted PNM files. If your environment uses GIMP on workstations, VDI instances, shared Linux desktops, or content-processing jump boxes, the practical risk is that a user opens a crafted file and triggers memory corruption in a desktop application that may have access to local files, credentials, tokens, or browser session artifacts.

Affected Versions and Fix Status

The versioning picture is incomplete, so it is important to be precise.

Because the fixed release number was not visible in the consulted sources, do not rely on assumptions such as “latest 3.2.x is safe” unless your package maintainer or upstream release notes explicitly say the build contains commit 83699817 or references CVE-2026-58380. For practitioners, the safest path is to validate either the exact release note or the distro package changelog rather than infer patch status from branch naming alone.

Technical Notes

To inventory installed GIMP versions on Linux endpoints, use package manager queries such as:

# Debian/Ubuntu
dpkg -l | grep -i '^ii.*gimp'

# RHEL/CentOS/Fedora
rpm -qa | grep -i '^gimp'

# Arch
pacman -Q | grep -i '^gimp'

If you build from source or package internally, verify whether the source tree contains the upstream fix commit:

git log --oneline --grep="83699817"
git show 83699817

Exploitation Status and PoC Availability

At the time of writing, there is no verified evidence of exploitation in the wild in the consulted sources. CVE-2026-58380 is not listed in CISA KEV, which means there is no CISA-backed confirmation of known exploitation. That does not prove it is unexploited, but it does mean defenders should not state exploitation as confirmed.

There is also no public proof-of-concept identified in the research provided here. However, the bug is not purely theoretical. Public technical tracking exists in both GNOME GitLab and Red Hat Bugzilla, and the visible upstream issue metadata indicates the crash was reproducible with ASAN. That matters because reproducible sanitizer-backed crashes often lower the barrier to future exploit development, even if exploit code is not yet public. The correct practitioner stance is: no confirmed in-the-wild exploitation, no known public PoC from the consulted sources, but credible technical validation exists.

Technical Deep Dive

The core bug is an off-by-one boundary error in pnmscanner_gettoken(). According to NVD, the parser writes a trailing NUL byte one position beyond a stack buffer while processing crafted PNM input. This is a classic parser hardening failure: tokenization logic often assumes input lengths remain within expected bounds, and a single incorrect comparison can turn a safe truncation path into an out-of-bounds write.

The reason defenders should care about a one-byte write is that stack corruption does not need to be large to be dangerous. Even when modern mitigations prevent reliable code execution, crashes are often enough to create denial-of-service conditions in user workflows or batch image processing. In some build environments, the overwritten byte could affect adjacent state in ways that become exploitable. Since public technical discussion and a fix commit exist, this is the kind of bug that may attract further scrutiny from researchers even if exploitation is not yet public.

Technical Notes

Relevant vulnerable area from the public descriptions:

pnmscanner_gettoken()

The trigger condition described by NVD is a specially crafted PNM file. Defenders who do malware triage should preserve suspicious PNM samples and capture crash artifacts such as core dumps, ASAN output, and the exact GIMP build used. If you operate a sandbox or detonation pipeline for attachments, adding GIMP-based rendering tests for uncommon image formats like PNM can improve visibility into malformed-file attacks.

Bottom Line for Defenders

CVE-2026-58380 is a high-severity GIMP parser vulnerability with a clear malformed-file attack path and an upstream fix already available. The strongest confirmed facts are that the bug affects GIMP’s PNM parser, was reproduced on GIMP 3.2.1, and is fixed upstream in commit 83699817.

What remains unknown is the full affected version range and the first fixed release number from the retrieved primary sources. In the absence of that data, defenders should assume any GIMP deployment at or around 3.2.1 needs validation, prioritize upgrades from trusted vendor channels, and treat untrusted PNM files as potentially dangerous until patch status is confirmed.

For further information on security practices, consider exploring what is defense in depth and what is OIDC.

This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.