CVE-2026-4887: Gimp: gimp:memory disclosure and denial of service via specially crafted pcx image
A flaw was found in GIMP. This issue is a heap buffer over-read in GIMP PCX file loader due to an off-by-one error. A remote attacker could exploit this by convincing a user to open a specially crafted PCX image. Successful exploitation could lead to out-of-bounds memory disclosure and a possible application crash, resulting in a Denial of Service (DoS).
CVE-2026-4887 affects GIMP when a user opens a malicious PCX image. The likely impact is application crash and limited memory disclosure, not system takeover. Business urgency is moderate: prioritize endpoints or servers where GIMP is installed and users handle untrusted image files.
Executive priority
Treat as a routine but timely desktop/application patching issue. Prioritize creative, support, and engineering teams that receive external image files. This is not currently supported as an actively exploited or remote unauthenticated server compromise issue by the provided sources.
Technical view
GIMP’s PCX file loader has a heap buffer over-read caused by an off-by-one error, mapped to CWE-193. CVSS 3.1 is 6.1 with user interaction required, low confidentiality impact, no integrity impact, and high availability impact. Red Hat lists multiple RHEL 8 and 9 GIMP packages affected; RHEL 7 affected; RHEL 6 status unknown.
Likely exposure
Exposure is most relevant on Red Hat systems with GIMP installed, especially RHEL 7, RHEL 8 AppStream, and RHEL 9 AppStream or SAP/EUS/TUS variants listed by Red Hat. Exploitation requires a user to open a crafted PCX file.
Exploitation context
The source bundle does not indicate active exploitation, and KEV is false. Abuse depends on social engineering or file-handling workflows that deliver PCX images to GIMP users. The described outcomes are out-of-bounds memory disclosure and possible crash.
Researcher notes
Key uncertainty is fix detail per stream; the bundle references multiple RHSAs but does not provide full remediation metadata. Avoid assuming impact beyond the stated PCX loader over-read. RHEL 6 is listed with unknown status, so confirm directly with Red Hat if still in scope.
Mitigation direction
Apply the relevant Red Hat security advisory updates for affected RHEL channels.
Check Red Hat CVE guidance for your exact product stream and package version.
Limit opening PCX files from untrusted sources until patched.
Remove GIMP where it is not business-required.
Educate users handling images about malicious file risk.
Validation and detection
Inventory systems with GIMP installed across RHEL 7, 8, and 9.
Map installed packages to Red Hat’s affected product list.
Confirm applicable RHSA advisories are installed for each RHEL stream.
Review image-processing workflows that accept PCX files from external parties.
Track Red Hat Bugzilla and GNOME issue updates for status changes.
Based on public source material and reviewed before publication.
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-193: 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.
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.
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-193 · source CWE mapping
Off-by-one Error
Off-by-one Error represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.