CVE-2025-14422VulnerabilityPublished 28 Jan 2026Updated 8 Oct 2026

SUSE · security update for gimp

Affects SUSESource GCVE Database

Mentioned vulnerabilities

Not known to be exploited.

Data as of 26 Oct 2026, 06:26 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SUSE Product Security Team SUSE	Affected Red Hat Red Hat Enterprise Linux Red Hat Enterprise Linux AppStream EUS (v.9.6) src gimp-2:2.99.8-4.el9_6.4.src SUSE aarch64 gimp-3.0.6-bp160.2.1.aarch64 gimp-devel-3.0.6-bp160.2.1.aarch64 gimp-extension-goat-excercises-3.0.6-bp160.2.1.aarch64 i686 gimp-libs-2:2.99.8-4.el9_6.4.i686 x86_64 gimp-2:2.99.8-4.el9_6.4.x86_64	Fixed in–

AI-suggested

Red Hat has released updated GIMP packages (version 2.99.8-4.el9_6.4) that fix these vulnerabilities. Users of affected Red Hat Enterprise Linux 9.6 Extended Update Support and related variants should apply the security update promptly. Refer to the Red Hat advisory RHSA-2026:1511 and the linked article https://access.redhat.com/articles/11258 for detailed update instructions. No other mitigation or workaround is indicated in the advisory.

Description

This update for gimp fixes the following issues: Changes in gimp: - CVE-2025-14422: Fixed PNM File Parsing Integer Overflow (bsc#1255293) - CVE-2025-14423: Fixed LBM File Parsing Stack-based Buffer Overflow (bsc#1255294) - CVE-2025-14424: Fixed XCF File Parsing Use-After-Free (bsc#1255295) - CVE-2025-14425: Fixed JP2 File Parsing Heap-based Buffer Overflow(bsc#1255296)

Impact

Successful exploitation of these vulnerabilities could allow an attacker to execute arbitrary code remotely by convincing a user to open a maliciously crafted PNM or JP2 image file in GIMP. This could lead to full compromise of the affected system under the privileges of the user running GIMP. The vulnerabilities are rated as high severity by the source data, indicating significant risk if unpatched.

Summary

The GNU Image Manipulation Program (GIMP) contained two security flaws that could allow remote code execution. The first is an integer overflow vulnerability in the parsing of PNM image files (CVE-2025-14422), and the second is a heap-based buffer overflow in JP2 image file parsing (CVE-2025-14425). Both vulnerabilities could be exploited by specially crafted image files to execute arbitrary code. Red Hat Product Security rated the update as Important and released patched versions of GIMP for Red Hat Enterprise Linux 9.6 Extended Update Support and related distributions. The advisory references fixes in gimp-2.99.8-4.el9_6.4 packages across multiple architectures.

CWE-190Integer Overflow or Wraparound (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
Requirements
Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.3 (opens in a new tab)
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-122Heap-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #16
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
Pre-design: Use a language or compiler that performs automatic bounds checking.
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Jul 2026, 10:16 UTC

WeaknessesCWE-190, CWE-122

Technical details

References

Community reviews

Related threats