Answer in brief
CVE-2026-82324 records a Medium severity (CVSS 6.1) vulnerability in Gimp: heap out-of-bounds reads in iff/ilbm loader from ham row size mismatch and nplanes=0. The current sources do not mark it as known exploited. The current feed maps GNOME/gimp (generic), Red Hat/gimp (generic), GNOME/GIMP (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps GNOME/gimp (generic), Red Hat/gimp (generic), GNOME/GIMP (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:gimp:gimp:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:redhat:enterprise_linux:6.0:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:redhat:enterprise_linux:7.0:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:redhat:enterprise_linux:8.0:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:redhat:enterprise_linux:9.0:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| GNOME/gimpgeneric | >=3.0.0 <* | * |
| Red Hat/gimpgeneric | * | Not reported |
| GNOME/GIMPgeneric | >=3.0.0 <* | * |
Published upstream
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 31, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 28, 2026
A flaw was found in the file-iff (IFF/ILBM) plugin in GIMP. When processing a specially crafted IFF/ILBM image file, the plugin does not properly validate the HAM row size and improperly handles cases where the number of color planes (nPlanes) is zero. This causes a row size mismatch that bypasses memory bounds checking, resulting in heap out-of-bounds reads. This issue can result in an application crash, leading to a denial of service or a limited information disclosure of heap memory contents.
Quoted source text, attributed separately from HOL analysis.