Bug 2457530 (CVE-2026-4154) - CVE-2026-4154 gimp: GIMP: Remote Code Execution via XPM File Parsing Integer Overflow
Summary: CVE-2026-4154 gimp: GIMP: Remote Code Execution via XPM File Parsing Integer ...
Keywords:
Status: NEW
Alias: CVE-2026-4154
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2457745
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-04-11 01:01 UTC by OSIDB Bzimport
Modified: 2026-05-14 11:55 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:16484 0 None None None 2026-05-12 23:44:07 UTC
Red Hat Product Errata RHSA-2026:17533 0 None None None 2026-05-14 11:55:08 UTC

Description OSIDB Bzimport 2026-04-11 01:01:22 UTC
GIMP XPM File Parsing Integer 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 XPM files. The issue results from the lack of proper validation of user-supplied data, which can result in an integer overflow before allocating a buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-28901.

Comment 2 errata-xmlrpc 2026-05-12 23:44:06 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:16484 https://access.redhat.com/errata/RHSA-2026:16484

Comment 3 errata-xmlrpc 2026-05-14 11:55:07 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:17533 https://access.redhat.com/errata/RHSA-2026:17533


Note You need to log in before you can comment on or make changes to this bug.