Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver image with oversized width/height
-
ExploitVictim exports image to GIF in GIMP
-
Execution32-bit buffer-size computation overflows, undersizing allocation
-
ImpactHeap buffer overflow corrupts memory enabling crash or code execution
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, buffer size validation
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to use GIMP's GIF export plug-in to export an image whose width and height are large enough to overflow the 32-bit computation of the pixel buffer size; the oversized dimensions are the specific trigger. Limiting factors that reduce real-world risk: the vector is local (AV:L) with no remote path, the user must actively perform the GIF export (UI:R), and attack complexity is high (AC:H) because the attacker must craft or induce export of an image with specific extreme dimensions. No authentication is required (PR:N), but exploitation depends entirely on convincing a local user to export a malicious or abnormally large image. |
| Impact | This is a moderate-severity, genuinely low-urgency issue rather than a top priority. The Red Hat-supplied CVSS 3.1 vector (AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H, score 6.3) is internally consistent with the description: exploitation is local, requires user interaction (the victim must perform the GIF export), and carries high attack complexity because the attacker must get a specifically oversized image exported. No confidentiality impact (C:N) aligns with a memory-corruption bug whose realistic outcome is a crash (A:H) or potential code execution (I:H) in the GIMP process. No EPSS score, no CISA KEV listing, and no POC were provided in the input, so there are no exploitation-probability or active-exploitation signals to weigh - exploitation status is therefore 'no public exploit identified at time of analysis'. Note a sourcing nuance: the affected-product metadata (CPE/tags) lists Red Hat Enterprise Linux 6-10, but the description makes clear the actual vulnerable software is GIMP's GIF export plug-in, which RHEL merely ships - verify affected-version scope against the GIMP project advisory, not just the RHEL CPE strings. Net assessment: a real but hard-to-weaponize desktop-application bug requiring local access and deliberate user action; not a mass-exploitation candidate. |
| Exploit ScenarioDerived | An attacker distributes (or convinces a victim to create) an image with extreme width and height values and persuades the user to export it as a GIF in GIMP. During export the 32-bit pixel-buffer-size computation overflows, so GIMP allocates an undersized heap buffer while GEGL writes using the true, larger image extent, corrupting heap memory and potentially leading to a crash or code execution in the user's context. No public exploit code was identified in the provided data, and the high attack complexity plus required user interaction make this difficult to trigger reliably. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Integer overflow in GIMP's GIF export plug-in leads to a heap-based buffer overflow when a user exports an image whose width and height are large enough to wrap the 32-bit pixel-buffer size calculation, resulting in an out-of-bounds write that can crash the application or corrupt memory. Affected software is the GIMP package as distributed in Red Hat Enterprise Linux 6, 7, 8, 9 and 10, and exploitation is local (AV:L) with high attack complexity (AC:H) and mandatory user interaction (UI:R) while requiring no privileges (PR:N) - the attacker must induce a user to export an image with extreme dimensions. No public exploit identified at time of analysis, and the independent assessment rates this a moderate-severity, genuinely low-urgency issue rather than a top priority.
RemediationAI
No vendor-released patch identified at time of analysis; the only supplied references are the Red Hat CVE page (https://access.redhat.com/security/cve/CVE-2026-106064) and the Bugzilla tracking entry (https://bugzilla.redhat.com/show_bug.cgi?id=2547446), so remediation should begin by monitoring those advisories for updated gimp packages and applying the fixed build as soon as Red Hat publishes it. Until then, the most effective specific mitigation is to prohibit or carefully control GIF exports from images with unusually large dimensions, since the trigger is the oversized width/height pair rather than file contents alone; requiring users to downscale, crop or convert oversized images before GIF export removes the integer-overflow precondition, at the cost of some workflow friction. On shared or high-value systems, further reduce exposure by removing, disabling or replacing the GIF export plug-in, or by running GIMP in a sandboxed low-privilege container so that any out-of-bounds write is confined; both measures reduce functionality but limit the blast radius. Given the local vector, high attack complexity and user-interaction requirement (AV:L/AC:H/UI:R) and the absence of confirmed active exploitation, these compensating controls are proportionate to a moderate-severity, low-urgency risk.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is a 32-bit integer overflow in the pixel-buffer size computation performed inside GIMP's GIF export plug-in, a weakness classed as CWE-119 (improper restriction of operations within the bounds of a memory buffer). When image width and height are large enough that the computed buffer size exceeds the range of a 32-bit integer, the value wraps to a much smaller number; the plug-in allocates a heap buffer of that wrapped size, but the GEGL processing pipeline then writes pixel data using the true, unwrapped image extent, producing a heap-based out-of-bounds write. The CVSS:3.1 vector AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H confirms a local attack path with high complexity, no required privileges, mandatory user interaction, and high integrity and availability impact but no confidentiality impact, so the realistic consequence is memory corruption and application crash or data corruption rather than a demonstrated code-execution primitive. The provided CPE entries map the issue to GIMP as shipped in Red Hat Enterprise Linux 6, 7, 8, 9 and 10, indicating a distribution-level advisory response rather than a standalone upstream CPE.
Know when Gimp gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H
Local file-processing flaw (AV:L) needing a crafted oversized image and a user-initiated export, so AC:H and UI:R with PR:N; memory corruption yields integrity/availability impact (I:H/A:H) but no direct confidentiality loss (C:N).
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
DescriptionCVE.org
A heap-based buffer overflow was found in GIMP’s GIF export plug-in. Exporting an image with very large width and height can cause 32-bit overflow when computing the pixel buffer size. The plug-in allocates a buffer based on the wrapped value while GEGL writes using the true image extent, rooted in integer overflow
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Affected Products (CPE)CVE.org
Buffer overflow in the readstr_upto function in plug-ins/script-fu/tinyscheme/scheme.c in GIMP 2.6.12 and earlier, and p
Multiple stack-based buffer overflows in file-xwd.c in the X Window Dump (XWD) plug-in in GIMP 2.8.2 allow remote attack
In GIMP 2.8.22, there is a heap-based buffer overflow in read_channel_data in plug-ins/common/file-psp.c. Rated high sev
fits-io.c in GIMP before 2.8.1 allows remote attackers to cause a denial of service (NULL pointer dereference and applic
An issue in gimp_layer_invalidate_boundary of GNOME GIMP 2.10.30 allows attackers to trigger an unhandled exception via
GIMP 2.10.30 and 2.99.10 are vulnerable to Buffer Overflow. Rated medium severity (CVSS 5.5), this vulnerability is no a
GIMP through 2.10.2 makes g_get_tmp_dir calls to establish temporary filenames, which may result in a filename that alre
Critical remote code execution vulnerability in GIMP's ICO file parser caused by an integer overflow (CWE-190) that lack
Remote code execution in GIMP 3.0.6 allows attackers to run arbitrary code by tricking a user into opening a malicious P
Remote code execution in GIMP 3.2.0-rc1 lets attackers run arbitrary code by tricking a user into opening a malicious IC
Use-after-free vulnerability in the xcf_load_image function in app/xcf/xcf-load.c in GIMP allows remote attackers to cau
Heap-based buffer overflow in GIMP's TIF file parser enables remote code execution when a user opens a crafted TIFF imag
EUVD-2026-94364
GHSA-v6pf-7x6j-gpfr
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB