CVE-2026-40916: Gimp: gimp: denial of service due to stack buffer overflow in tim image loader
A flaw was found in GIMP. A stack buffer overflow vulnerability in the TIM image loader's 4BPP decoding path allows a local user to cause a Denial of Service (DoS). By opening a specially crafted TIM image file, the application crashes due to an unconditional overflow when writing to a variable-length array.
Security readout for executives and security teams
Plain-English summary
CVE-2026-40916 is a GIMP crash vulnerability triggered by opening a specially crafted TIM image. The disclosed impact is denial of service: the application crashes. The provided sources do not show data theft, privilege escalation, remote compromise, or active exploitation.
Executive priority
Treat as a routine-to-moderate desktop application risk. Prioritize systems used for image handling or exposed to external files. Business impact is application availability, not confirmed system compromise.
Technical view
GIMP’s TIM image loader has a stack buffer overflow in the 4BPP decoding path. The flaw writes unconditionally to a variable-length array, causing a crash. CVSS 3.1 is 5.0 with local access, low complexity, low privileges, and user interaction required.
Likely exposure
Exposure is likely on Red Hat Enterprise Linux 6, 7, 8, and 9 systems with the affected GIMP packages installed. Practical risk centers on users who open untrusted or externally supplied TIM image files.
Exploitation context
The source bundle states this is local and requires a crafted file to be opened. CISA KEV status is false in the provided data. No cited source supports active exploitation or remote attack capability.
Researcher notes
Classified as CWE-787 out-of-bounds write. The affected component is the TIM loader 4BPP decode path. Evidence provided names Red Hat packaged GIMP on RHEL 6 through 9; do not generalize beyond cited affected products without additional vendor data.
Mitigation direction
Check Red Hat CVE and Bugzilla pages for fixed package availability or official workarounds.
Update affected GIMP packages when vendor fixes are available.
Avoid opening untrusted TIM image files until vendor guidance is applied.
Remove GIMP from systems where it is not required.
Validation and detection
Inventory RHEL 6, 7, 8, and 9 systems with GIMP installed.
Identify workflows that receive TIM files from untrusted sources.
Review Red Hat advisory status for CVE-2026-40916.
Confirm remediation by verifying installed packages against vendor guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-787 · source CWE mapping
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.