Is CVE-2026-106063 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-106063 being exploited in the wild.

How severe is CVE-2026-106063?

Medium severity, with a CVSS score of 6.3, published 6 October 2026.

How is CVE-2026-106063 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-106063?

Check whether you run GIMP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-106063: GIMP heap buffer overflow in DICOM export

Q: Is there a fix for CVE-2026-106063?

No fixed version is recorded yet. Avoid exporting untrusted or unnecessarily large images to DICOM format. Cap image dimensions in workflows that process third-party content, and use checked multiplication and maximum dimension limits in custom automation that drives GIMP export. [{"kind": "disclosed", "at": "2026-10-06"}] If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

CVE-2026-106063 · Severity: medium · CVSS 6.3 · Published 2026-10-06

GIMP is a widely-used image editing application. The DICOM export feature (used to save medical images) contains a flaw where exporting an image with extremely large dimensions can cause GIMP to crash or corrupt memory. An attacker could trigger this by tricking a user into exporting a specially crafted oversized image file to DICOM format.

Technologies: GIMP.

Quick answers

Is CVE-2026-106063 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-106063 being exploited in the wild.
How severe is CVE-2026-106063?: Medium severity, with a CVSS score of 6.3, published 6 October 2026.
Which products and versions are affected?: GIMP <unknown.
Is there a fix for CVE-2026-106063?: No fixed version is recorded yet. Avoid exporting untrusted or unnecessarily large images to DICOM format. Cap image dimensions in workflows that process third-party content, and use checked multiplication and maximum dimension limits in custom automation that drives GIMP export.</anigation> <parameter name="timeline">[{"kind": "disclosed", "at": "2026-10-06"}] If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-106063 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-106063?: Check whether you run GIMP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Avoid exporting untrusted or unnecessarily large images to DICOM format. Cap image dimensions in workflows that process third-party content, and use checked multiplication and maximum dimension limits in custom automation that drives GIMP export.</anigation> <parameter name="timeline">[{"kind": "disclosed", "at": "2026-10-06"}]

Technical details

A heap-based buffer overflow occurs in GIMP's DICOM export plug-in when a 32-bit integer multiplication of width × height × bytes-per-pixel overflows, allocating an undersized buffer. GEGL then writes the full uncompressed image data into this undersized buffer (CWE-787). The attack requires user interaction—the user must explicitly export an oversized image to DICOM format; merely opening a malicious file is insufficient.

Affected products

GIMP <unknown

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.