Code execution via unchecked JP2 length
Published Apr 11, 2026 · Updated Apr 11, 2026
Heap-based buffer overflow in GIMP 3.0.8 allows remote attackers to execute arbitrary code through a crafted JP2 file. The JP2 parser copies user-supplied data into a heap buffer without validating that its encoded length fits the destination. Execution requires the target to open the file or visit a page that causes GIMP to process it, and code runs in the current process.
Summary
What happened
Heap-based buffer overflow in GIMP 3.0.8 allows remote attackers to execute arbitrary code through a crafted JP2 file. The JP2 parser copies user-supplied data into a heap buffer without validating that its encoded length fits the destination. Execution requires the target to open the file or visit a page that causes GIMP to process it, and code runs in the current process.
The record
- CVE
- CVE-2026-4152
- Published
- Apr 11, 2026
- Updated
- Apr 11, 2026
- Vendor
- GIMP
- Product
- GIMP
- Classifications
- CWE-787, CWE-131, CWE-122, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 11, 2026CVE publishedPublication date reported by the CVE source.
- Apr 11, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0.8
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo