Code execution via TIF parsing stack overflow
Published Aug 20, 2026 · Updated Aug 21, 2026
Stack-based buffer overflow in TIF parsing in GIMP 3.2.2 allows remote attackers to execute arbitrary code via a crafted TIF file. The TIF parser copies user-supplied data into a stack buffer without validating the length first, so a malformed image can overwrite stack memory while GIMP processes the file. Exploitation requires user interaction such as opening a malicious image or visiting a page that causes GIMP to parse it, and code runs in the context of the current GIMP process.
Summary
What happened
Stack-based buffer overflow in TIF parsing in GIMP 3.2.2 allows remote attackers to execute arbitrary code via a crafted TIF file. The TIF parser copies user-supplied data into a stack buffer without validating the length first, so a malformed image can overwrite stack memory while GIMP processes the file. Exploitation requires user interaction such as opening a malicious image or visiting a page that causes GIMP to parse it, and code runs in the context of the current GIMP process.
The record
- CVE
- CVE-2026-18303
- Published
- Aug 20, 2026
- Updated
- Aug 21, 2026
- Vendor
- GIMP
- Product
- GIMP
- Classifications
- CWE-121, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 20, 2026CVE publishedPublication date reported by the CVE source.
- Aug 21, 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.2.2
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