PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-106063 Red Hat CVE debrief

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 (CWE-787), after integer overflow in the allocation size.

Vendor
Red Hat
Product
Red Hat Enterprise Linux 10
CVSS
MEDIUM 6.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-06
Original CVE updated
2026-10-07
Advisory published
2026-10-06
Advisory updated
2026-10-07

Who should care

Defenders responsible for GIMP installations, especially in environments where untrusted images are processed, should assess exposure and prioritize verification and patching. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify GIMP installations, assess image processing workflows, and monitor for patches or updates from the vendor.

Why it matters

Defenders should prioritize verifying and patching GIMP installations, especially in environments where untrusted images are processed, to prevent potential buffer overflow and exploitation.

  • Verify GIMP installations for potential exposure to heap buffer overflow
  • Assess image processing workflows for untrusted input to prevent potential buffer overflow
  • Monitor for patches or updates from the vendor to address the buffer overflow vulnerability

Technical summary

The CVE record describes a heap-based buffer overflow 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 (CWE-787), after integer overflow in the allocation size. This vulnerability affects GIMP installations, especially in environments where untrusted images are processed, and defenders should prioritize verifying and patching.

Defensive priority

Defenders should prioritize verifying and patching GIMP installations, especially in environments where untrusted images are processed.

Recommended defensive actions

  • Verify GIMP installations for potential exposure
  • Assess image processing workflows for untrusted input
  • Monitor for patches or updates from the vendor
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the heap-based buffer overflow in GIMP’s DICOM export plug-in. Specific version information and remediation steps are not provided. However, defenders should verify GIMP installations, especially in environments where untrusted images are processed, and monitor for patches or updates from the vendor. The CVE record was published on 2026-10-06T19:34:29.710Z and has not been modified since then. Evidence limits are constrained by available information.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-106063 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-106063

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-106063 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-106063

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.