CVE-2026-78465
CVE-2026-78465 — Gimp: integer overflow in pcx loader (planes=4) leads to heap overflow on 32-bit
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.
Published Updated Sources: NVD, Red Hat (CNA), GitHub, GitHub Security Advisory, Red Hat (VEX), SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Exploit code
public exploit, none observed
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
7
high
Remediation
The vendor's own words where we have them.
Upgrade Red Hat Enterprise Linux 6 to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
Red Hat VEX · CVE-2026-78465
workaround: To mitigate this vulnerability, do not open PCX files from untrusted sources with GIMP.
no_fix_planned: Out of support scope
none_available: Affected
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Prioritize based on EPSS, PoC availability, and external exposure.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| Red Hat | Red Hat Enterprise Linux 6 | — | Vulnerable |
| Red Hat | Red Hat Enterprise Linux 7 | — | Vulnerable |
| Red Hat | Red Hat Enterprise Linux 8 | — | Vulnerable |
| Red Hat | Red Hat Enterprise Linux 9 | — | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
High
Confidentiality
High
Integrity
High
Scope
Unchanged
Attack Complexity
High
Attack Vector
Local
Privileges Req
None
User Interaction
Required
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7 | CVSS 3.1 | high | 1 | 5.9 | Red Hat (CNA), GHSA, Red Hat (VEX) |
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
What this weakness leads to
MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.
CWE-190 · Integer Overflow or Wraparound
- DoS: Crash, Exit, or Restart
- DoS: Resource Consumption (CPU)
- DoS: Resource Consumption (Memory)
- DoS: Instability
Mitigation: Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
Weakness & attack patterns
- CWE-190Integer Overflow or Wraparound
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Repositories
1
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · CVSS 3.1 7.0 (AV:L)
Aug 24, 2026 · NVD
Initial · CVE published
Aug 24, 2026 · NVD
Reported to Red Hat.
Aug 24, 2026 · Red Hat
Added · GHSA-944m-78f8-q7cr published (high)
Aug 24, 2026 · GitHub Security Advisory
CVE published by mitre
Aug 24, 2026 · SOCRadar CTI
Reported · Made public.
Jul 24, 2026 · Red Hat
Source activity
Readings a source repeats on a schedule, counted rather than listed.
- 1×CVE modified by NIST, Modified, LinkAug 24, 2026 · SOCRadar CTI
References
6 on the record
- access.redhat.com/security/cve/CVE-2026-78465
Vendor Advisory, NIST
- bugzilla.redhat.com/show_bug.cgi?id=2522057
Vendor Advisory, Mitre, NIST
- gitlab.gnome.org/GNOME/gimp/-/work_items/16578
Vendor Advisory, NIST
- nvd.nist.gov/vuln/detail/CVE-2026-78465
NVD
- github.com/advisories/GHSA-944m-78f8-q7cr
Exploit, Third Party Advisory
- www.cve.org/CVERecord?id=CVE-2026-78465
Vendor Advisory
Elsewhere on this site
- Red Hatevery CVE for this vendor
- Memory Corruptionsame class
- CWE-190other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-78465 is Gimp: integer overflow in pcx loader (planes=4) leads to heap overflow on 32-bit, a high vulnerability affecting Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9 from Red Hat. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-78465. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.