GIMP
CVE-2025-10922
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious DCM file
-
DeliveryDeliver via web page or email
-
ExploitVictim opens file in GIMP
-
ExecutionOverflow heap buffer in DCM parser
-
ImpactExecute code as current user
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution 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 open or load an attacker-supplied DCM (DICOM) file in GIMP 3.0.4 - i.e., GIMP must actually invoke its DCM file-parsing code path on untrusted input. The key limiting factors are: mandatory user interaction (UI:R - the user must open the malicious file or visit a page that triggers the load), local processing (AV:L - no network-reachable service is exposed), and the specific file type (DICOM/.dcm), so environments that never handle DCM images or untrusted image files have markedly lower exposure. No authentication or elevated privileges are needed (PR:N), and the default GIMP configuration is sufficient; code executes with the privileges of the user running GIMP, not elevated. |
| Impact | This is a genuinely notable client-side RCE but not a drop-everything emergency. The CVSS 3.0 base score of 7.8 (High) reflects full compromise of confidentiality, integrity, and availability (C:H/I:H/A:H) but is gated by AV:L (local) and UI:R (required user interaction), meaning the attacker cannot reach the vulnerable code without a user voluntarily opening or loading a crafted DCM file. Note the apparent tension between the vendor/ZDI narrative ('remote attackers... visit a malicious page or open a malicious file') and the CVSS vector's AV:L: ZDI classifies file-delivered client-side bugs as local-vector because the malicious data is processed on the victim's machine, so this is file-borne rather than network-reachable - defenders should treat it as a phishing/malicious-file threat, not a remotely sprayable service exploit. No EPSS score, KEV listing, or public POC is present in the provided data, so exploitation is 'no public exploit identified at time of analysis'; the only exploit evidence is ZDI's private proof-of-concept behind advisory ZDI-25-911. On balance this is a real priority for organizations where GIMP is used to process untrusted images (especially DICOM/DCM workflows), but the UI:R requirement and absence of active-exploitation signals place it below internet-facing unauthenticated RCEs. |
| Exploit ScenarioDerived | An attacker crafts a malicious DCM (DICOM) image file with an oversized length field and delivers it via a web page, email attachment, or shared medical-imaging dataset. When a victim opens the file in GIMP 3.0.4, the parser copies the attacker-controlled data into an undersized heap buffer, corrupting heap memory and allowing arbitrary code execution in the context of the user running GIMP. A private proof-of-concept exists with ZDI (ZDI-CAN-27863 / ZDI-25-911), but no public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 19, 2026
Heap-based buffer overflow in GIMP 3.0.4's DCM file parser allows arbitrary code execution when a user opens a crafted .dcm image; the code runs with the privileges of the GIMP process. Exploitation requires user interaction and no authentication, and no public exploit has been identified at time of analysis. The vendor has published an upstream fix commit, and Debian 11 users should review the LTS advisory; the client-side file-open prerequisite keeps practical exposure lower than a remotely reachable service.
RemediationAI
Apply the upstream GIMP fix commit 3d909166463731e94dfe62042d76225ecfc4c1e4 or upgrade to a GIMP release that contains it; a specific released patched version is not independently confirmed in the provided data, so verify the fixed package version with the vendor or distribution. Debian 11 users should follow the Debian LTS announcement at https://lists.debian.org/debian-lts-announce/2025/10/msg00022.html and install the updated package when available. If immediate patching is not possible, avoid opening untrusted .dcm files and disable or remove the DCM plug-in when DICOM support is not required, accepting loss of DICOM import functionality; alternatively, run GIMP in a sandbox (e.g., Flatpak/Snap confinement or an OS sandbox) to reduce the impact of successful exploitation, with the trade-off of restricted file and desktop integration. Review the ZDI advisory at https://www.zerodayinitiative.com/advisories/ZDI-25-911/ for additional details.
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
GIMP's DCM plug-in parses DICOM images, a medical-imaging format, and the flaw is a CWE-122 heap-based buffer overflow caused by missing validation of user-supplied length data before a heap copy. The assessed CVSS 3.1 vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H shows the attack is local to the file-open action, unauthenticated, and requires the victim to load a crafted .dcm file; no network service is exposed. CPE data identifies GIMP 3.0.4 and Debian Linux 11.0 as affected, and the upstream fix is in GitLab commit 3d909166463731e94dfe62042d76225ecfc4c1e4.
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:L/PR:N/UI:R/S:U/C:H/I:H/A:H
File-delivered parser bug: AV:L and UI:R because the victim must open a crafted DCM locally, PR:N as no auth is needed, and C/I/A:H since arbitrary code runs as the user.
Primary rating from Vendor (trendmicro).
CVSS VectorVendor: trendmicro
DescriptionCVE.org
GIMP DCM File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GIMP. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.
The specific flaw exists within the parsing of DCM files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-27863.
Executive ViewAI
GIMP 3.0.4 contains a heap-based buffer overflow in its DCM file parser that can allow a crafted image to execute code with the GIMP user’s privileges. The risk is concentrated in design, media, and other teams that routinely open external image files; exploitation requires a user to open a malicious .dcm file, and no public exploit has been identified at time of analysis, but a successful attack could compromise the endpoint under the logged-in user’s permissions. Leadership should prioritize patching and user guidance because the impact is local code execution rather than a remotely reachable service outage.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
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.
A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
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
GitHub PoC
Exploit-DB