Quick answers
- Is CVE-2026-106062 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106062 being exploited in the wild.
- How severe is CVE-2026-106062?
- High severity, with a CVSS score of 7.8, published 6 October 2026.
- Which products and versions are affected?
- GIMP GIMP.
- Is there a fix for CVE-2026-106062?
- No fixed version is recorded yet. Do not open DDS files from untrusted sources. Exploitation may be harder on hardened systems with Full RELRO/PIE, ASLR, FORTIFY_SOURCE, and heap allocator protections enabled. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-106062 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-106062?
- Check whether you run Gimp. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
Do not open DDS files from untrusted sources. Exploitation may be harder on hardened systems with Full RELRO/PIE, ASLR, FORTIFY_SOURCE, and heap allocator protections enabled.
Technical details
A heap-based buffer overflow exists in GIMP's DDS loader due to integer overflow in size calculations (CWE-190) using 32-bit arithmetic for buffer dimensions. The allocated buffer becomes too small for the amount of pixel data written through GEGL, causing out-of-bounds writes (CWE-787). The attack is local and requires user interaction to open a crafted file; exploitation may grant arbitrary code execution within the GIMP process context.
Affected products
- GIMP GIMP
Timeline
- 2026-10-06: disclosed