CVE-2026-4887
Gimp ≤ 3.2.0
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:HSummary
CVE-2026-4887 is a medium-severity Off-by-one Error (CWE-193) vulnerability in Gimp Gimp. Its CVSS base score is 6.1 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 47th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-4887 is a heap buffer over-read vulnerability in the PCX file loader of GIMP, stemming from an off-by-one error. This flaw affects the GIMP image editing software, as documented in the CVE published on 2026-03-26. It is classified under CWE-193 (Off-by-one Error) with a CVSS v3.1 base score of 6.1 (AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H).
A remote attacker can exploit this vulnerability by convincing a user to open a specially crafted PCX image file. Exploitation triggers an out-of-bounds memory read, potentially disclosing sensitive memory contents and causing an application crash that results in a denial-of-service (DoS) condition.
Advisories and patches addressing this issue are detailed in Red Hat's security notice at https://access.redhat.com/security/cve/CVE-2026-4887, Red Hat Bugzilla entry https://bugzilla.redhat.com/show_bug.cgi?id=2451669, and GIMP's GitLab issue tracker at https://gitlab.gnome.org/GNOME/gimp/-/issues/15960.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-16166
Vulnerability Data
A flaw was found in GIMP. This issue is a heap buffer over-read in GIMP PCX file loader due to an off-by-one error. A remote attacker could exploit this by convincing a user to open a specially crafted PCX image.…
more
Successful exploitation could lead to out-of-bounds memory disclosure and a possible application crash, resulting in a Denial of Service (DoS).
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.2.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover off-by-one errors in loops, bounds, and calculations before deployment.
Requiring documented development standards and tools can embed bounds-checking and arithmetic-correctness rules that stop off-by-one mistakes at introduction.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent off-by-one errors via reviews, static analysis, and testing.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect off-by-one errors before release.
Secure development life cycle includes requirements and reviews that can catch off-by-one errors.
Application security requirements can specify bounds-checking and input validation to prevent off-by-one errors.
Secure system architecture and engineering principles promote defensive coding practices that reduce off-by-one mistakes.
Secure coding directly addresses off-by-one errors through coding standards and peer review.