CVE-2026-0797
Heap-Based Buffer Overflow in GIMP ICO Parsing Enables RCE
Publication date: 2026-02-20
Last updated on: 2026-02-24
Assigner: Zero Day Initiative
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gimp | gimp | 3.2.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-122 | A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). |
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a heap-based buffer overflow in the way GIMP parses ICO files. Specifically, it occurs because the software does not properly validate the length of user-supplied data before copying it into a heap-based buffer. This flaw can be exploited by remote attackers to execute arbitrary code on the affected system.
Exploitation requires user interaction, such as opening a malicious ICO file or visiting a malicious webpage that triggers the vulnerability.
How can this vulnerability impact me? :
If exploited, this vulnerability allows an attacker to execute arbitrary code within the context of the current process running GIMP. This can lead to full compromise of the affected system, including unauthorized access, data theft, or further malware installation.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know