GIMP JP2 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 JP2 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-28863.
Security readout for executives and security teams
Plain-English summary
CVE-2026-4152 is a high-severity flaw in GIMP's JP2 image handling. A malicious JP2 file or webpage could trigger memory corruption and run code as the user opening it. Exploitation requires user interaction, but impact includes compromise of confidentiality, integrity, and availability.
Executive priority
Prioritize within normal high-severity desktop patching SLAs, faster for creative, marketing, support, or intake teams that process external images. The issue can lead to code execution, but requires user interaction and has no cited active exploitation evidence.
Technical view
The flaw is a heap-based buffer overflow in JP2 parsing caused by insufficient validation of user-supplied length before copying to a heap buffer. The provided CVSS is 7.8 with user interaction required and high confidentiality, integrity, and availability impact. The bundle identifies GIMP 3.0.8 as affected.
Likely exposure
Exposure is most likely on workstations or servers where GIMP 3.0.8 is installed and users open JP2 images from email, web downloads, tickets, shared drives, or customer submissions.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. ZDI describes remote attackers needing the target to open a malicious file or visit a malicious page, which limits automation but still supports targeted phishing or file-sharing scenarios.
Researcher notes
Focus assessment on JP2 parsing paths in GIMP 3.0.8 and downstream package status. The bundle cites CWE-122 and CWE-131, ZDI-CAN-28863, a GIMP commit, and Red Hat advisories, but does not provide exploit details or a fixed upstream version.
Mitigation direction
Identify systems with GIMP 3.0.8 installed.
Apply vendor updates referenced by GIMP and Red Hat advisories when applicable.
Block or quarantine untrusted JP2 files where business workflows allow.
Warn users not to open unexpected JP2 files or image links.
Check vendor guidance because no fixed GIMP version is named in the bundle.
Validation and detection
Inventory installed GIMP versions across managed endpoints.
Confirm whether Linux packages map to the referenced Red Hat advisories.
Review email, web, and file-sharing controls for JP2 attachment handling.
Verify updated packages or builds include the referenced GIMP commit.
Monitor endpoint telemetry for unexpected GIMP crashes or suspicious 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-122: 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
12Source 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-122 · source CWE mapping
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Calculation of Buffer Size represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.