Quick answers
- Is CVE-2026-106067 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106067 being exploited in the wild.
- How severe is CVE-2026-106067?
- Medium severity, with a CVSS score of 6.3, published 7 October 2026.
- Which products and versions are affected?
- GIMP <UNKNOWN>.
- Is there a fix for CVE-2026-106067?
- No fixed version is recorded yet. Do not run the Hot filter or similar heavy filters on untrusted images with extreme dimensions; limit canvas size in untrusted workflows. 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-106067 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-106067?
- Check whether you run GIMP at an affected version. 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 run the Hot filter or similar heavy filters on untrusted images with extreme dimensions; limit canvas size in untrusted workflows.
Technical details
A heap-based buffer overflow exists in GIMP's Hot color filter due to integer overflow in 32-bit width × height arithmetic during pixel buffer allocation, while the filter's pixel access path uses the true image dimensions. This causes the allocated buffer to be smaller than the data the filter processes, resulting in an out-of-bounds write. The vulnerability requires user interaction (running the filter on an oversized image) and is not triggered by merely opening a file.
Affected products
- GIMP <UNKNOWN>
Timeline
- 2026-10-07: disclosed