GIMP PSP 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 PSP 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-28874.
Security readout for executives and security teams
Plain-English summary
A malicious PSP image can cause vulnerable GIMP to run attacker-controlled code when a user opens it or is led to a malicious page. This is most urgent for desktops, design teams, and automated image-processing workflows using GIMP. The sources do not show confirmed active exploitation.
Executive priority
Treat as high priority for workstations and image-processing environments. The business risk is code execution after user interaction, especially in creative or support teams that regularly handle outside files. Patch and reduce untrusted PSP exposure promptly.
Technical view
The flaw is in GIMP PSP file parsing. Insufficient validation of user-supplied length data before copying into a heap buffer can trigger a heap-based buffer overflow, mapped to CWE-120 and CWE-122. CVSS is 7.8 with user interaction required and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely on endpoints or processing systems with GIMP 3.0.8 or downstream packages that parse PSP files. Internet-facing services are not identified in the sources, but workflows accepting untrusted image files increase risk.
Exploitation context
The attacker must persuade a user to open a malicious file or visit a malicious page. Successful exploitation may execute code in the current GIMP process context. KEV status is false, and the bundle provides no confirmed active exploitation evidence.
Researcher notes
Evidence supports a PSP parser heap overflow with RCE impact and required user interaction. The affected entry names GIMP 3.0.8, while downstream status should be verified through vendor package advisories. No exploit proof, KEV listing, or broader affected-version range is provided in the bundle.
Mitigation direction
Update GIMP or downstream packages using vendor guidance and Red Hat errata where applicable.
Prioritize systems that open untrusted images or process uploaded PSP files.
Restrict PSP file handling from email, web downloads, and external submissions until patched.
Prefer sandboxed image-processing workflows for files from untrusted sources.
Monitor vendor advisories for fixed release details beyond the referenced commit.
Validation and detection
Inventory installed GIMP versions and identify any 3.0.8 deployments.
Check Linux package versions against the relevant Red Hat errata or vendor advisory.
Confirm fixes include the GNOME GIMP commit referenced for CVE-2026-4153.
Review workflows where GIMP processes externally supplied PSP files.
Look for unexpected GIMP launches tied to recent downloads or email attachments.
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
17Source 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.