CVE-2026-78465
Received Received - Intake

Integer Overflow in GIMP File-PCX Plugin

Publication date: 2026-08-24

Last updated on: 2026-08-24

Assigner: redhat-SADP

Description
A flaw was found in the file-pcx plugin in GIMP, affecting 32-bit builds only. When processing a PCX image file, the plugin calculates memory allocation sizes based on the image dimensions and the number of color planes. If a crafted file sets the number of planes to 4 alongside sufficiently large dimensions, the calculation exceeds the 32-bit integer limit and overflows, resulting in an undersized heap-based buffer allocation. This integer overflow issue results in a heap-based buffer overflow when the plugin subsequently writes image data into the undersized buffer, causing memory corruption, potentially leading to arbitrary code execution or a denial of service.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-24
Last Modified
2026-08-24
Generated
2026-08-24
AI Q&A
2026-08-24
EPSS Evaluated
N/A
NVD
CVE-2026-78465
EUVD
EUVD-2026-64935

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
gimp file-pcx *
gnome gimp to 32-bit (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-190 The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects only 32-bit builds of GIMP's file-pcx plugin. When processing a crafted PCX image file with 4 color planes and large dimensions, the plugin miscalculates memory allocation sizes due to an integer overflow. This causes the plugin to allocate a buffer too small for the actual data, leading to a heap-based buffer overflow when writing image data. The flaw can result in memory corruption, potentially allowing arbitrary code execution or a denial of service.

Detection Guidance

Detecting this vulnerability requires checking for GIMP installations and specifically the file-pcx plugin on 32-bit systems. Inspect GIMP version and plugin files for the affected component. No direct network detection commands exist, but monitoring for crashes when opening PCX files may indicate exploitation attempts.

Impact Analysis

If you use a 32-bit build of GIMP and open a specially crafted PCX file from an untrusted source, this vulnerability could allow attackers to execute arbitrary code on your system or cause a denial of service. Exploitation requires user interaction, such as opening the malicious file.

Compliance Impact

This vulnerability could impact compliance by potentially allowing unauthorized code execution or data corruption on systems handling sensitive data. Organizations using 32-bit GIMP builds may need to assess risks to data confidentiality and integrity under regulations like GDPR or HIPAA, especially if the software processes personal or health information.

Mitigation Strategies

Avoid opening PCX files from untrusted sources in GIMP. Update GIMP to the latest version if a patch is available. On 32-bit systems, consider using 64-bit builds of GIMP if possible. Enable security features like ASLR, NX stack protection, and SELinux if available.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-78465. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart