Gimp: gimp: integer overflow in read_rle_channel() (CVE-2026-58384) | HOL Guard CVE

High · CVSS 7.3CVE-2026-58384

Gimp: gimp: integer overflow in read_rle_channel()

Answer in brief

CVE-2026-58384 records a High severity (CVSS 7.3) vulnerability in Gimp: gimp: integer overflow in read_rle_channel(). The current sources do not mark it as known exploited. Affected software not mapped in the current feed; confirm the named product and version against your inventory.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Jul 7, 2026Updated Sep 30, 2026Source checked Sep 30, 2026First seen by HOL Jul 7, 2026Material review Sep 30, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.3
Exploitation: Not marked as known exploited
Affected software: Not mapped
Fix availability: Not reported

Why this deserves its current priority

CVSS is 7.3. 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.

Affected scope and exposure questions

Affected software not mapped in the current feed; confirm the named product and version against your inventory.

Recommended response

Confirm exposure. Identify whether the named product or interface exists in your inventory, then review the linked upstream references for affected versions and vendor guidance.

Evidence timeline and material changes

Published upstream
Jul 7, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jul 7, 2026

Sources and claim methodology

Upstream source description

A flaw was found in GIMP's PSD parser. An integer overflow in read_RLE_channel() can cause an undersized heap allocation for the RLE row-length table, after which subsequent per-row writes corrupt heap memory. This could lead to memory corruption, potentially resulting in denial of service or arbitrary code execution.

Quoted source text, attributed separately from HOL analysis.