CVE-2026-4152
Heap-Based Buffer Overflow in GIMP JP2 Parsing Enables RCE
Publication date: 2026-04-11
Last updated on: 2026-04-14
Assigner: Zero Day Initiative
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gimp | gimp | 3.0.8 |
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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows remote attackers to execute arbitrary code with high impact on confidentiality, integrity, and availability of the affected system. Such a compromise could lead to unauthorized access or disclosure of sensitive data, which may affect compliance with standards like GDPR and HIPAA that require protection of personal and health information.
However, the provided information does not explicitly detail the direct impact on compliance with these regulations.
Can you explain this vulnerability to me?
CVE-2026-4152 is a heap-based buffer overflow vulnerability in GIMP's JP2 file parsing functionality. The flaw occurs because the software does not properly validate the length of user-supplied data before copying it into a heap-based buffer.
To exploit this vulnerability, an attacker needs user interaction, such as the target opening a malicious JP2 file or visiting a malicious webpage.
If successfully exploited, the attacker can execute arbitrary code with the privileges of the current process running GIMP.
How can this vulnerability impact me? :
This vulnerability can allow remote attackers to execute arbitrary code on your system with the same privileges as the GIMP process.
Such code execution can compromise the confidentiality, integrity, and availability of your system and data.
Because exploitation requires user interaction, the risk depends on whether a user opens a malicious JP2 file or visits a malicious webpage.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should update GIMP to the latest version where this heap-based buffer overflow issue in JP2 file parsing has been fixed.
Additionally, avoid opening JP2 files from untrusted sources or visiting suspicious webpages that might exploit this vulnerability, as exploitation requires user interaction.