CVE-2025-10920: gimp security update
Affects gimpSource GCVE Database
Not known to be exploited : upgrade to 2:3.0.4-1.el9_7.1 soon.
Data as of 20 Nov 2026, 01:36 UTC
Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
- Patch
- Available – fixed in 2:3.0.4-1.el9_7.1
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 19 Nov 2026.
What to do
Upgrade the AlmaLinux to 2:3.0.4-1.el9_7.1.
Patches and advisories
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AlmaLinux 9gimp | Affected
| Fixed in
|
| AlmaLinux 9gimp-libs | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A security update fixing these vulnerabilities is available in GIMP version 2:3.0.4-1.el9_7.1 for Red Hat Enterprise Linux 9. Users should apply this update promptly to remediate the vulnerabilities. No additional mitigation steps are indicated by the vendor advisory.
Description
Multiple remote code execution vulnerabilities have been identified in GIMP related to parsing various image file formats, including ICNS, DCM, WBMP, HDR, ILBM, FF, and XWD. These vulnerabilities involve heap-based buffer overflows, out-of-bounds writes, stack-based buffer overflows, and integer overflows. An important security update addressing these issues is available in GIMP version 2:3.0.4-1.el9_7.1 for Red Hat Enterprise Linux 9.
References
- access.redhat.com/errata/RHSA-2025:21968 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-10920 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-10921 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-10922 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-10923 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-10924 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-10925 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-10934 (opens in a new tab)
- bugzilla.redhat.com/2407188 (opens in a new tab)
- bugzilla.redhat.com/2407191 (opens in a new tab)
- bugzilla.redhat.com/2407192 (opens in a new tab)
- bugzilla.redhat.com/2407194 (opens in a new tab)
- bugzilla.redhat.com/2407199 (opens in a new tab)
- bugzilla.redhat.com/2407200 (opens in a new tab)
- bugzilla.redhat.com/2407233 (opens in a new tab)
- errata.almalinux.org/9/ALSA-2025-21968.html (opens in a new tab)