Quick answers
- Is CVE-2026-106066 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106066 being exploited in the wild.
- How severe is CVE-2026-106066?
- Medium severity, with a CVSS score of 6.3, published 7 October 2026.
- Which products and versions are affected?
- GIMP GIMP.
- Is there a fix for CVE-2026-106066?
- No fixed version is recorded yet. Avoid raw export of untrusted or abnormally large images; validate image dimensions before automated export operations.</anigation> <parameter name="timeline">[{"kind": "disclosed", "at": "2026-10-07"}] 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-106066 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-106066?
- 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
Avoid raw export of untrusted or abnormally large images; validate image dimensions before automated export operations.</anigation> <parameter name="timeline">[{"kind": "disclosed", "at": "2026-10-07"}]
Technical details
A heap-based buffer overflow exists in GIMP's raw data export plug-in due to integer overflow in buffer size calculations (width * height * bytes-per-pixel). When g_malloc() allocates memory based on this overflowed value, it reserves far less memory than GEGL later reads or writes during export, causing out-of-bounds memory access. The attack requires local access and user interaction to export a malicious or abnormally large image; the resulting memory corruption can crash the application or potentially enable code execution.
Affected products
- GIMP GIMP