Skip to content
VulniPulse
Advisory severityHigh7.0Red Hat Linux

High [CVE-2026-62439] Gimp: gimp: file-pvr plug-in pvr file parsing integer overflow heap-based buffer overflow vulnerability

This high-severity Red Hat Linux advisory covers CVE-2026-62439 affecting Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-62439 Source published Source updated

VulniPulse record published

CVE-2026-62439
Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open source advisory

Get an email when Red Hat Linux RHEL & SELinux publishes the next one.

See Red Hat Linux RHEL & SELinux's last 90 days of advisories first. Then choose the free weekly digest, or a free month of real-time alerts with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat Linux RHEL & SELinux

Summary

A flaw was found in GIMP. An integer overflow occurs in the file-pvr plug-in when calculating memory buffer sizes for image dimensions.

By tricking a user into opening or previewing a specially crafted PowerVR (.pvr) file, an attacker can trigger a heap-based buffer overflow, potentially leading to arbitrary code execution or a Denial of Service (DoS) via an application crash. Red Hat severity: Important — CVSS 7 (CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H).

Weakness: CWE-190. Affected Red Hat products: Red Hat Enterprise Linux 6; Red Hat Enterprise Linux 7; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9.

Will not fix / out of support: Red Hat Enterprise Linux 6. Red Hat does not currently list a fixing RHSA for this CVE.

Affected products named by the advisory: Red Hat package: gimp.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.

Official advisory · high-confidence parse· fetched 12 days ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists. Confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 12 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce checked arithmetic and header dimension bounds verification before allocating pixel destination buffers in the file-pvr plug-in: upgrade to the fixed Gimp/Gimp:2.8/Gimp builds, which validate header width and height dimensions against MAX_TWIDDLE_SIZE and use checked multiplication for buffer size calculations, closing all 2 injection vectors (opening a crafted .pvr file in GIMP, thumbnailing or previewing a crafted .pvr file). Until patched, this is a concern on Users and automated indexing or thumbnailing services processing PowerVR (.pvr) files, so Avoid opening untrusted PowerVR (.pvr) texture files in GIMP and disable automated thumbnail generation or file indexer processing for .pvr files. As a compensating measure, Compile with signed integer overflow trapping (-ftrapv or UndefinedBehaviorSanitizer) to abort execution if buffer size arithmetic overflows. These controls limit blast radius and contain exploitation, but they do not fix the underlying integer overflow and heap buffer overflow defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1311 Input Size and Quantity Bounds Enforcement (high)

Official advisory · high-confidence parse· fetched 12 days ago·verify at source

All Red Hat Linux advisories

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.