GIMP ICO File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GIMP. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.
The specific flaw exists within the parsing of ICO files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-28599.
Security readout for executives and security teams
Plain-English summary
CVE-2026-0797 is a high-severity GIMP flaw where a crafted ICO image can cause memory corruption and potentially run code as the user. It requires user interaction, such as opening a malicious file or visiting a malicious page. The known affected version in the bundle is GIMP 3.2.0-RC1.
Executive priority
Prioritize patching or removing affected GIMP builds on user workstations and image-processing systems. The risk is high because successful exploitation can run code, but urgency is lower than a wormable or confirmed exploited vulnerability because user interaction is required and KEV is false.
Technical view
The flaw is a heap-based buffer overflow in GIMP ICO parsing caused by insufficient validation of user-supplied length before copying data. ZDI describes arbitrary code execution in the current process context. The CVSS 3.1 score is 8.8 with network attack vector, low complexity, no privileges, and required user interaction.
Likely exposure
Exposure is most likely on endpoints or image-processing workflows running GIMP 3.2.0-RC1 or downstream packages assessed by vendors. The bundle does not prove broader GIMP version impact beyond the listed affected version.
Exploitation context
The source bundle says exploitation requires user interaction. CISA KEV status is false, and no provided source states active exploitation. Treat this as credible RCE risk, but not as confirmed in-the-wild exploitation.
Researcher notes
Key evidence comes from ZDI, the CVE record, a GNOME GIMP commit reference, and Red Hat advisories. Public sources identify ICO parsing, heap overflow, and RCE impact, but the bundle does not include proof of active exploitation or complete cross-version affectedness.
Mitigation direction
Identify and remove GIMP 3.2.0-RC1 where present.
Apply vendor GIMP fixes or applicable Red Hat errata packages.
Restrict opening untrusted ICO files until patched.
Use endpoint controls for files downloaded from web or email.
Monitor vendor advisories for confirmed fixed versions.
Validation and detection
Inventory installed GIMP versions across workstations and build images.
Check package status against Red Hat errata where applicable.
Confirm whether GIMP 3.2.0-RC1 exists in developer environments.
Review detections for suspicious GIMP crashes or child processes.
Verify user workflows that process ICO files from external sources.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
16Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-120 · source CWE mapping
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.