CVE-2026-62439

Fixes and workarounds

Workaround

--- 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)