cve.bz

CVE-2026-106063

6.3 mediumEPSS 0.1%

Medium (6.3). EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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

Severity

CVSS 3.1

6.3 medium
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-106063 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106063?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106063?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-106063 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13gimpno fix listedDEBIAN-CVE-2026-106063
Debian14gimp3.2.8-1DEBIAN-CVE-2026-106063
Ubuntu26.04:LTS, 26.10, Pro:16.04:LTS and 4 moregimpno fix listedUBUNTU-CVE-2026-106063
SUSELinux Enterprise Module for Package Hub 15 SP7, Linux Enterprise Workstation Extension 15 SP7gimp2.10.30-150400.3.85.1SUSE-SU-2026:4895-1
openSUSELeap 16.0gimp3.0.8-bp160.13.1openSUSE-SU-2026:22123-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A heap-based buffer overflow was found in GIMP when exporting images to the DICOM format. If a user exports an image with dimensions large enough to cause integer overflow in buffer size calculations, GIMP may write past the end of a heap-allocated buffer. This could crash GIMP or corrupt memory. Exploitation requires the user to export an oversized image; opening a small malicious file alone is insufficient.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10gimpFix deferred
Red Hat Enterprise Linux 6gimpOut of support scope
Red Hat Enterprise Linux 7gimpOut of support scope
Red Hat Enterprise Linux 8gimp:2.8/gimpFix deferred
Red Hat Enterprise Linux 9gimpFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-106063.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-119 (12).

References

Check your stackJSON