Skip to main content
VulnerabilityPublished Updated

CVE-2026-106062: GIMP’s DirectDraw Surface (DDS) loader · Heap-based Buffer Overflow Was Found

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-106062· High 7.8

Not known to be exploited · CVSS 7.8 High : patch Red Hat Enterprise Linux 9 soon.

Data as of 2 Nov 2026, 22:58 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.17.8
EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat Enterprise Linux 9gimpAffected–Fixed in–
Red Hat Enterprise Linux 10gimpAffected–Fixed in–
Red Hat Enterprise Linux 6gimpAffected–Fixed in–
Red Hat Enterprise Linux 7gimpAffected–Fixed in–
Red Hat Enterprise Linux 8gimp:2.8/gimpAffected–Fixed in–

Description

A heap-based buffer overflow was found in GIMP’s DirectDraw Surface (DDS) loader. When loading a crafted DDS image, buffer sizes derived from width, height, and pitch can be computed using 32-bit arithmetic that overflows. The allocated buffer is too small for the amount of pixel data written through GEGL (CWE-787), following integer overflow in size calculations (CWE-190). This may allow heap corruption and, in the worst case, arbitrary code execution in the context of the GIMP process.

References

Community reviews

Loading reviews…