CVE-2026-0797 | GIMP ICO File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability

GIMP ICO 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 ICO 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-28599.

Published: 2026-02-20 Last update: 2026-02-24 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-0797 is rated Moderate Risk (48.1/100): CVSS High severity, with low exploitation likelihood (EPSS 0.66%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-0797

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.03% 0.66% +0.63%
2 2026-03-21 0.06% 0.03% -0.02%
3 2026-02-21 — 0.06% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-0797

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.0 HIGH
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]

Weakness enumeration for CVE-2026-0797

OS Trackers for CVE-2026-0797

vendor priority summary link
alpine — CVE-2026-0797: 1 source package rows (gimp); 1 state rows across 1 repos (edge-community); fixed 0, open 1. https://security.alpinelinux.org/vuln/CVE-2026-0797
debian not yet assigned CVE-2026-0797 not yet assigned priority: Debian including 1 source packages (gimp), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2026-0797
redhat high — https://access.redhat.com/security/cve/CVE-2026-0797
suse high CVE-2026-0797 severity important: SUSE including 30 source package names (gimp-2.10.30-150400.3.41.1, gimp-2.8.22-26.module+el8.10.0+24086+d017a7e0.5, …), 49 product×package rows across 5 product lines (SUSE Liberty Linux 8, SUSE Liberty Linux 9, … (5 product lines)): Fixed 49. https://www.suse.com/security/cve/CVE-2026-0797/
ubuntu medium CVE-2026-0797 medium priority: Ubuntu including 1 source packages (gimp), 7 status rows across 7 suites (bionic, focal, jammy, noble, questing, upstream, xenial): needs-triage 7. https://ubuntu.com/security/CVE-2026-0797

Affected software / configurations for CVE-2026-0797

Vendor Product Version Raw CPE
gimp gimp 3.2.0 cpe:2.3:a:gimp:gimp:3.2.0:rc1:*:*:*:*:*:*

References for CVE-2026-0797

cvelogic Threat Intelligence