RHSA-2026:61587HighCVSS 8.4

Red Hat Security Advisory: gimp security update

Published
August 31, 2026
Last Modified
October 12, 2026

🔗 CVE IDs covered (9)

CVE-2026-18301 →CVE-2026-18304 →CVE-2026-18306 →CVE-2026-18308 →CVE-2026-59090 →CVE-2026-18302 →CVE-2026-18303 →CVE-2026-18305 →CVE-2026-18307 →

📋 Description

CVE-2026-18301 — gimp: GIMP: Remote code execution via PSD file parsing integer overflow CVE-2026-18302 — gimp: GIMP: Remote code execution via TIF file parsing heap-based buffer overflow CVE-2026-18303 — gimp: GIMP: Remote code execution via TIF file parsing vulnerability CVE-2026-18304 — gimp: GIMP: Arbitrary code execution via crafted TIF file parsing CVE-2026-18305 — gimp: GIMP: Remote Code Execution via TIF file parsing integer overflow CVE-2026-18306 — gimp: GIMP: Remote Code Execution via SGI File Parsing Integer Overflow CVE-2026-18307 — gimp: GIMP: Remote code execution via TIF file parsing heap-based buffer overflow CVE-2026-18308 — gimp: GIMP: Remote Code Execution via TIF File Parsing Integer Overflow CVE-2026-59090 — gimp: GIMP: Arbitrary code execution in PSD plugin due to unsigned underflow

🎯 Affected products25

  • Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-2:3.0.4-4.el9_8.10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-2:3.0.4-4.el9_8.10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-2:3.0.4-4.el9_8.10.src as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-2:3.0.4-4.el9_8.10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-debuginfo-2:3.0.4-4.el9_8.10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-debuginfo-2:3.0.4-4.el9_8.10.i686 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-debuginfo-2:3.0.4-4.el9_8.10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-debuginfo-2:3.0.4-4.el9_8.10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-debugsource-2:3.0.4-4.el9_8.10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-debugsource-2:3.0.4-4.el9_8.10.i686 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-debugsource-2:3.0.4-4.el9_8.10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-debugsource-2:3.0.4-4.el9_8.10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-devel-tools-debuginfo-2:3.0.4-4.el9_8.10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-devel-tools-debuginfo-2:3.0.4-4.el9_8.10.i686 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-devel-tools-debuginfo-2:3.0.4-4.el9_8.10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-devel-tools-debuginfo-2:3.0.4-4.el9_8.10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-libs-2:3.0.4-4.el9_8.10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-libs-2:3.0.4-4.el9_8.10.i686 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-libs-2:3.0.4-4.el9_8.10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-libs-2:3.0.4-4.el9_8.10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-libs-debuginfo-2:3.0.4-4.el9_8.10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-libs-debuginfo-2:3.0.4-4.el9_8.10.i686 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-libs-debuginfo-2:3.0.4-4.el9_8.10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • gimp-libs-debuginfo-2:3.0.4-4.el9_8.10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: To mitigate this issue, users should avoid opening untrusted or suspicious PSD files with GIMP. As GIMP is a desktop application that processes untrusted content, exercising caution with the origin of files is a primary defense. No specific configuration or operational controls are available to prevent exploitation without patching. Workaround: To mitigate this issue, users should exercise caution and avoid opening TIF image files from untrusted or unknown sources. As a general security practice, only process files from trusted origins. Workaround: To mitigate this vulnerability, users should avoid opening TIF image files from untrusted or unknown sources. As this flaw requires user interaction to open a malicious file, exercising caution with file origins can prevent exploitation. Workaround: Since this vulnerability requires user interaction with a malicious file, users should exercise caution when opening TIF image files from untrusted sources. To further reduce risk, consider running GIMP within a sandboxed environment, such as a container or Flatpak, to limit the potential impact of a successful exploit. Workaround: To mitigate this vulnerability, avoid opening TIF image files from untrusted or unknown sources in GIMP. This operational control prevents the application from processing malicious input that could lead to arbitrary code execution. Workaround: To mitigate this issue, users should avoid opening untrusted SGI image files with GIMP. If GIMP is not required, consider removing the `gimp` package from the system. Workaround: To mitigate this vulnerability, users should avoid opening untrusted TIF image files with GIMP. If GIMP is not required, consider removing the package from the system. For systems where GIMP is necessary, exercise caution when handling TIF files from unknown or suspicious sources. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Workaround: To mitigate this vulnerability, users should avoid opening untrusted or suspicious PSD image files with GIMP. As a general security practice, it is recommended to only process image files from trusted sources.

🔗 References (12)