CVE-2026-4153 | GIMP PSP File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability

GIMP PSP 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 PSP 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-28874.

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

CVE-2026-4153 is rated Low Risk (37.5/100): CVSS High severity, with low exploitation likelihood (EPSS 0.06%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

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-4153

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-04-11 — 0.06% —

Full EPSS history (1 record total)

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

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-4153

OS Trackers for CVE-2026-4153

vendor priority summary link
debian not yet assigned CVE-2026-4153 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-4153
redhat high — https://access.redhat.com/security/cve/CVE-2026-4153
suse high CVE-2026-4153 severity important: SUSE including 17 source package names (gimp-2.10.30-150400.3.50.1, gimp-3.0.8-bp160.3.1, …), 28 product×package rows across 4 product lines (SUSE Linux Enterprise Module for Package Hub 15 SP7, SUSE Linux Enterprise Workstation Extension 15 SP7, openSUSE Leap 15.6, openSUSE Leap 16.0): Fixed 28. https://www.suse.com/security/cve/CVE-2026-4153/
ubuntu medium CVE-2026-4153 medium priority: Ubuntu including 1 source packages (gimp), 7 status rows across 7 suites (bionic, focal, jammy, noble, questing, upstream, xenial): needs-triage 6, released 1. https://ubuntu.com/security/CVE-2026-4153

Affected software / configurations for CVE-2026-4153

Vendor Product Version Raw CPE
gimp gimp 3.0.8 cpe:2.3:a:gimp:gimp:3.0.8:*:*:*:*:*:*:*

References for CVE-2026-4153

cvelogic Threat Intelligence