CVE-2026-2272 json
Gimp: gimp: memory corruption due to integer overflow in ico file handling
published 2026-03-26 7 mo ago modified 2026-11-05 3 d ago also EUVD-2026-16341
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
A flaw was found in GIMP. An integer overflow vulnerability exists when processing ICO image files, specifically in the `ico_read_info` and `ico_read_icon` functions. This issue arises because a size calculation for image buffers can wrap around due to a 32-bit integer evaluation, allowing oversized image headers to bypass security checks. A remote attacker could exploit this by providing a specially crafted ICO file, leading to a buffer overflow and memory corruption, which may result in an application level denial of service.
Patch / fix
- gimp Debian 12 2.10.34-1+deb12u8
- gimp Debian 13 3.0.4-3+deb13u6
- gimp Debian 14 3.2.0~RC2-3.2
debian advisories DEBIAN-CVE-2026-2272
- gimp SLE Workstation Extension 15 SP7, SLE Module for Package Hub 15 SP7, openSUSE Leap 15.6 2.10.30-150400.3.44.1
suse advisories SUSE-SU-2026:0604-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-2272 updated cvss 4.3
gimp: GIMP: Memory corruption due to integer overflow in ICO file handling
-
Red Hat Enterprise Linux 6 gimp, gimp-libs, gimp-devel-tools, gimp-help-browseraffected: workaround, no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 gimp, gimp-libs, gimp-devel-tools Red Hat Enterprise Linux 8 gimp, pygtk2, gimp-libs, pygobject2, python2-cairo, pygtk2-codegen, +3 more Red Hat Enterprise Linux 9 gimp, gimp-libsaffected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7 mo ago
Exploit prediction
0.87% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=2438428 referenced PoC, tagged "exploit" by a source, unverified
- gitlab.gnome.org https://gitlab.gnome.org/GNOME/gimp/-/issues/15617 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
Affected products
- Red Hat Red Hat Enterprise Linux 6
- Red Hat Red Hat Enterprise Linux 7
- Red Hat Red Hat Enterprise Linux 8
- Red Hat Red Hat Enterprise Linux 9
Classification
- Weakness
-
- CWE-190 Integer Overflow or Wraparound
References
-
bugzilla.redhat.com
/show_bug.cgi?id=2438428
issue-tracking, exploit, third-party-advisory
-
gitlab.gnome.org
/GNOME/gimp/-/issues/15617
exploit, issue-tracking
-
access.redhat.com
/security/cve/CVE-2026-2272
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2026-2272
- NVD CVE-2026-2272
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.