CVE-2026-62439
Description
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.
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)
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7 | N/A | 7 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | High | N/A | High |
| Privileges Required | None | N/A | None |
| User Interaction | Required | N/A | Required |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Acknowledgements
Red Hat would like to thank Florent Saudel for reporting this issue.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
