A heap-buffer-overflow vulnerability exists in the APNG (Animated PNG) file loader of GIMP. This flaw occurs when the fcTL width exceeds the IHDR width, leading to pixel data being written past the end of a heap allocation. Additionally, a heap-based buffer overflow exists in the DDS plug-in due to a BPP mismatch in the load_layer() function. Both vulnerabilities can be triggered by opening a specially crafted image file, potentially leading to code execution.
CVE-2026-42169
This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.1% (2nd percentile of EPSS-scored CVEs). GitHub Security Advisory enrichment pending alignment with NVD CVSS.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 7.8HIGHmedium confidence
- EG Risk
- 35EG Risk 35/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity78% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.1%
- EPSS %ILE
- 2nd
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
August 4, 2026
Last Modified
September 30, 2026
Advisory Details (2)
Auto-updated Aug 4, 20262461725 – (CVE-2026-42169) CVE-2026-42169 gimp: GIMP APNG loader heap-buffer-overflow when fcTL width exceeds IHDR width (file-png.c)
https://bugzilla.redhat.com/show_bug.cgi?id=2461725CVE-2026-42169 - Red Hat Customer Portal
Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a
https://access.redhat.com/security/cve/CVE-2026-42169Vendor Advisories for CVE-2026-42169(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:73768Red Hat Product SecurityHigh
Red Hat Security Advisory: gimp security update
- RHSA-2026:50817Red Hat Product SecurityHigh
Red Hat Security Advisory: gimp security update
- GHSA-xq2c-w9r3-rwr6GitHub Security AdvisoriesHigh
A heap-buffer-overflow vulnerability exists in the APNG (Animated PNG) file loader of GIMP. This...
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | gimp-2:2.99.8-4.el9_6.20 | 2026-09-30 | redhat |
| redhat | gimp-2:3.0.4-4.el9_8.9 | 2026-08-05 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| gimp | 2.10.22-4 ... 3.2.4-3 (61 versions) |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| gimp | 2.10.34-1 ... 3.2.4-3 (56 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| gimp | 3.0.4-3 ... 3.2.4-3 (28 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| gimp | 3.0.4-3 ... 3.2.2-1 (16 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 29× in last 7d / 128× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 298 total refreshes for this CVE.
- 2026-10-04 23:43 UTCVendor advisory
- 2026-10-04 23:43 UTCGHSA enrichment
- 2026-10-04 06:15 UTCEG score recompute
- 2026-10-04 06:15 UTCVendor advisory
- 2026-10-04 06:15 UTCGHSA enrichment
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-03 02:01 UTCEG score recompute
- 2026-10-03 02:01 UTCVendor advisory
- 2026-10-03 02:01 UTCGHSA enrichment
- 2026-10-02 10:15 UTCEG score recompute
- 2026-10-02 10:15 UTCVendor advisory
- 2026-10-02 10:15 UTCGHSA enrichment
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-10-01 06:55 UTCVendor advisory
- 2026-10-01 06:55 UTCGHSA enrichment
- 2026-09-30 18:45 UTCEG score recompute▲ 0.50
- 2026-09-30 18:45 UTCVendor advisory
- 2026-09-30 18:45 UTCGHSA enrichment
- 2026-09-30 18:44 UTCNVD updateCVSS v3 → 7.8
- 2026-09-30 16:15 UTCEG score recompute
- 2026-09-30 16:15 UTCVendor advisory
- 2026-09-30 16:15 UTCGHSA enrichment
- 2026-09-30 15:03 UTCEPSS rescore
- 2026-09-30 15:02 UTCEG score recompute
- 2026-09-30 15:02 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-30 15:02 UTCGHSA enrichment
- 2026-09-29 06:28 UTCEG score recompute
- 2026-09-29 06:28 UTCVendor advisory
- 2026-09-29 06:28 UTCGHSA enrichment
- 2026-09-28 06:16 UTCVendor advisory
- 2026-09-28 06:16 UTCGHSA enrichment
- 2026-09-27 18:11 UTCEG score recompute
- 2026-09-27 18:11 UTCVendor advisory
- 2026-09-27 18:10 UTCGHSA enrichment
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-26 15:58 UTCEPSS rescore
- 2026-09-25 04:44 UTCEG score recompute
- 2026-09-25 04:44 UTCVendor advisory
- 2026-09-25 04:44 UTCGHSA enrichment
- 2026-09-24 04:24 UTCEG score recompute
- 2026-09-24 04:24 UTCVendor advisory
- 2026-09-24 04:24 UTCGHSA enrichment
- 2026-09-23 17:53 UTCEPSS rescore
- 2026-09-23 16:15 UTCVendor advisory
- 2026-09-23 16:15 UTCGHSA enrichment
- 2026-09-23 03:44 UTCVendor advisory
- 2026-09-23 03:44 UTCGHSA enrichment
- 2026-09-22 15:39 UTCEG score recompute
- 2026-09-22 15:39 UTCVendor advisory
- 2026-09-22 15:39 UTCGHSA enrichment
- 2026-09-22 03:34 UTCEG score recompute
- 2026-09-22 03:34 UTCVendor advisory
- 2026-09-22 03:34 UTCGHSA enrichment
- 2026-09-20 20:54 UTCEG score recompute
- 2026-09-20 20:54 UTCVendor advisory
- 2026-09-20 20:54 UTCGHSA enrichment
- 2026-09-20 20:15 UTCEPSS rescore
- 2026-09-19 23:24 UTCEG score recompute
- 2026-09-19 23:24 UTCVendor advisory
- 2026-09-19 23:24 UTCGHSA enrichment
- 2026-09-19 07:59 UTCEG score recompute
- 2026-09-19 07:59 UTCVendor advisory
- 2026-09-19 07:59 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 17:51 UTCVendor advisory
- 2026-09-18 17:51 UTCGHSA enrichment
- 2026-09-18 04:22 UTCEG score recompute
- 2026-09-18 04:22 UTCVendor advisory
- 2026-09-18 04:22 UTCGHSA enrichment
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-17 16:17 UTCVendor advisory
- 2026-09-17 16:17 UTCGHSA enrichment
- 2026-09-17 01:12 UTCEG score recompute
- 2026-09-17 01:12 UTCVendor advisory
- 2026-09-17 01:12 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:17 UTCVendor advisory
- 2026-09-16 05:17 UTCGHSA enrichment
- 2026-09-15 16:51 UTCEG score recompute
- 2026-09-15 16:51 UTCVendor advisory
- 2026-09-15 16:51 UTCGHSA enrichment
- 2026-09-15 01:44 UTCVendor advisory
- 2026-09-15 01:44 UTCGHSA enrichment
- 2026-09-14 08:53 UTCVendor advisory
- 2026-09-14 08:53 UTCGHSA enrichment
- 2026-09-13 20:48 UTCEG score recompute
- 2026-09-13 20:48 UTCVendor advisory
- 2026-09-13 20:48 UTCGHSA enrichment
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 08:40 UTCVendor advisory
- 2026-09-13 08:40 UTCGHSA enrichment
- 2026-09-12 20:35 UTCEG score recompute
- 2026-09-12 20:35 UTCVendor advisory
- 2026-09-12 20:35 UTCGHSA enrichment
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-12 08:30 UTCVendor advisory
- 2026-09-12 08:30 UTCGHSA enrichment
- 2026-09-11 20:24 UTCEG score recompute
- 2026-09-11 20:24 UTCVendor advisory
- 2026-09-11 20:24 UTCGHSA enrichment
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:11:gimp
- CVE-2010-4541EG 9.3EPSS p94HIGH
- CVE-2009-3909EG 9.3EPSS p95HIGH
- CVE-2009-1570EG 9.3EPSS p95HIGH
- CVE-2018-12713EG 9.1CRITICAL
- CVE-2023-44443NVD 7.8EG 9.0EPSS p100CRITICAL
- CVE-2026-2044EG 8.8HIGH
- CVE-2026-0797EG 8.8HIGH
- CVE-2025-5473EG 8.8EPSS p98HIGH
- CVE-2023-44442NVD 7.8EG 8.5EPSS p99HIGH
- CVE-2023-44444NVD 7.8EG 8.4EPSS p99HIGH
Same vendor
10 shownredhat:RHSA-2026:50817 · redhat:RHSA-2026:73768
Frequently asked(5)
What is CVE-2026-42169?
When was CVE-2026-42169 disclosed?
Is CVE-2026-42169 actively exploited?
What is the CVSS score of CVE-2026-42169?
How do I remediate CVE-2026-42169?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42169
Is Your Infrastructure Affected by CVE-2026-42169?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.