Description
A flaw was found in GIMP's PNM file format parser. When parsing a specially crafted PNM file, the pnmscanner_gettoken() function writes a null terminator one byte past the end of a stack-allocated buffer due to an off-by-one error in the loop boundary check. This could lead to memory corruption, potentially resulting in denial of service or arbitrary code execution.
Affected products
gimp: gimp; redhat: enterprise linux
References9
- gitlab.gnome.org/GNOME/gimp/-/issues/16206 ExploitIssue TrackingVendor Advisory
- access.redhat.com/errata/RHSA-2026:40751
- access.redhat.com/errata/RHSA-2026:62507
- access.redhat.com/errata/RHSA-2026:73768
- access.redhat.com/errata/RHSA-2026:80509
- access.redhat.com/errata/RHSA-2026:93589
- access.redhat.com/security/cve/CVE-2026-58380 Third Party Advisory
- bugzilla.redhat.com/show_bug.cgi?id=2496135 Issue TrackingThird Party Advisory
- gitlab.gnome.org/GNOME/gimp/-/commit/83699817 Broken Link
Metrics
- CVSS 3.1
-
7.8
HIGH
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 0% percentile: 25 · as of 15 November 2026
- CWE
- CWE-193
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.