Code execution via overflowing pixel-buffer allocation
Published Oct 16, 2026 · Updated Oct 16, 2026
Integer overflow in GIMP's file-pvr plug-in allows attackers to execute code or crash the application via crafted PVR files. The pvr_decode_compressed() function multiplies image width, height, and component count without overflow checks, allocating an undersized heap buffer. Exploitation requires opening or previewing the crafted file; the reported consequences are heap corruption, application crashes, and arbitrary code execution.
Summary
What happened
Integer overflow in GIMP's file-pvr plug-in allows attackers to execute code or crash the application via crafted PVR files. The pvr_decode_compressed() function multiplies image width, height, and component count without overflow checks, allocating an undersized heap buffer. Exploitation requires opening or previewing the crafted file; the reported consequences are heap corruption, application crashes, and arbitrary code execution.
The record
- CVE
- CVE-2026-62439
- Published
- Oct 16, 2026
- Updated
- Oct 16, 2026
- Vendor
- libuser Project
- Product
- Red Hat Enterprise Linux 9
- Classifications
- T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 16, 2026CVE publishedPublication date reported by the CVE source.
- Oct 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started