Code execution via unchecked Despeckle buffer sizing
Published Jun 13, 2025 · Updated Jun 30, 2026
Integer overflow in GIMP's Despeckle plug-in before 3.0.4 allows local users to execute code by processing a very large image. The plug-in multiplies image width, height, and bytes per pixel without overflow checks, allocates an undersized heap buffer, and writes beyond it. Exploitation requires user interaction to run Despeckle on attacker-controlled image dimensions and can corrupt the process heap, crash GIMP, or execute code with the user's privileges.
Summary
What happened
Integer overflow in GIMP's Despeckle plug-in before 3.0.4 allows local users to execute code by processing a very large image. The plug-in multiplies image width, height, and bytes per pixel without overflow checks, allocates an undersized heap buffer, and writes beyond it. Exploitation requires user interaction to run Despeckle on attacker-controlled image dimensions and can corrupt the process heap, crash GIMP, or execute code with the user's privileges.
The record
- CVE
- CVE-2025-6035
- Published
- Jun 13, 2025
- Updated
- Jun 30, 2026
- Vendor
- GIMP
- Product
- GIMP
- Classifications
- CWE-190, T1204.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 13, 2025CVE publishedPublication date reported by the CVE source.
- Jun 30, 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=0 <3.0.4
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