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
A malicious ICO image can trigger a memory corruption bug in affected GIMP installations. If a user opens the file or visits a malicious page that hands it to GIMP, attacker code could run with that user's privileges.
Executive priority
Prioritize remediation on user workstations and creative teams that handle external images. The risk is high because successful exploitation could run attacker code, but exposure requires user interaction and evidence of active exploitation is not provided.
Technical view
CVE-2026-0797 is a heap-based buffer overflow in GIMP ICO parsing. The flaw is insufficient validation of user-supplied length data before copying into a heap buffer. ZDI rates it CVSS 8.8, network reachable with user interaction and high confidentiality, integrity, and availability impact.
Likely exposure
Known affected evidence in the bundle names GIMP 3.2.0-RC1. Exposure is most likely on workstations, image-processing workflows, or package sets that open untrusted ICO files with vulnerable GIMP builds.
Exploitation context
The bundle states remote code execution is possible, but user interaction is required. It does not cite active exploitation, and KEV is false, so active exploitation should not be assumed.
Researcher notes
The key issue is ICO parser length validation leading to heap overflow. The source bundle names ZDI-CAN-28599 and a GNOME commit, but does not provide exploit details. Validate by version/package state and patch provenance, not by reproducing the bug in production.
Mitigation direction
Update GIMP using vendor or distribution guidance where fixed packages are available.
Avoid GIMP 3.2.0-RC1 for untrusted ICO files until remediated.
Treat externally supplied icon files as untrusted content.
Use OS sandboxing or workstation isolation for risky image review workflows.
Review Red Hat errata if using downstream packaged GIMP.
Validation and detection
Inventory installed GIMP versions across endpoints and build images.
Identify systems running GIMP 3.2.0-RC1 or affected downstream packages.
Confirm fixed vendor commit or distribution errata is present.
Check file association policies for ICO files on managed endpoints.
Review security tooling for suspicious GIMP crashes or spawned child processes.
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.