CVE-2026-106063

Gimp: gimp: heap buffer overflow in dicom export on oversized image dimensions

  • Medium 6.3

Description

A heap-based buffer overflow was found in GIMP’s DICOM export plug-in. When exporting an image with extremely large width and height, the export path allocates a buffer using a 32-bit width * height (and bytes-per-pixel) product that can overflow. GEGL then writes the full uncompressed extent into the undersized buffer, after integer overflow in the allocation size

Key facts

Published
6 Oct 2026
Last changed
5 Nov 2026
Assigned by
redhat
EPSS
0.119% likely to be exploited in the next 30 days, higher than 1.798% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 6.3CVSS 3.1, Mediumfrom the CNA (redhat)CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H

What to do

  • To mitigate this avoid exporting untrusted or unnecessarily huge images to DICOM; cap image dimensions in workflows that process third-party content. Use checked multiplication and maximum dimension limits in custom automation that drives GIMP export.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Enterprise Linux 10
  • Default status: affected
Red HatRed Hat Enterprise Linux 6
  • Default status: unknown
Red HatRed Hat Enterprise Linux 7
  • Default status: unknown
Red HatRed Hat Enterprise Linux 8
  • Default status: affected
Red HatRed Hat Enterprise Linux 9
  • Default status: affected

Timeline

  1. 22 Sep 2026 Reported to Red Hat.
  2. 6 Oct 2026 Made public.
  3. 6 Oct 2026 Published

Weakness

References