CVE-2026-42169

HIGHPre-NVD 7.37.3—
EchelonGraph scoreHIGH confidence

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-08-04. a secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.3
EG Score
7.3(high)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

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 computed
Severity73% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 6, 2026

Advisory Details (2)

Auto-updated Aug 4, 2026
Patch available. Sources: redhat.
redhat

2461725 – (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=2461725
redhat Patch Available

CVE-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-42169

Vendor Advisories for CVE-2026-42169(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatgimp-2:3.0.4-4.el9_8.92026-08-05redhat

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)
PackageVulnerable rangeFixed inDependents
gimp2.10.22-4 ... 3.2.4-3 (61 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
gimp2.10.34-1 ... 3.2.4-3 (56 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
gimp3.0.4-3 ... 3.2.4-3 (28 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
gimp3.0.4-3 ... 3.2.2-1 (16 versions)3.2.4-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 39× in last 7d / 101× 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 101 total refreshes for this CVE.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 20:10 UTCVendor advisory
  3. 2026-08-20 20:10 UTCGHSA enrichment
  4. 2026-08-20 08:05 UTCVendor advisory
  5. 2026-08-20 08:05 UTCGHSA enrichment
  6. 2026-08-19 20:00 UTCEG score recompute
  7. 2026-08-19 20:00 UTCVendor advisory
  8. 2026-08-19 20:00 UTCGHSA enrichment
  9. 2026-08-19 17:03 UTCEPSS rescore
  10. 2026-08-19 07:55 UTCVendor advisory
  11. 2026-08-19 07:55 UTCGHSA enrichment
  12. 2026-08-18 19:50 UTCEG score recompute
  13. 2026-08-18 19:50 UTCVendor advisory
  14. 2026-08-18 19:50 UTCGHSA enrichment
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-18 07:45 UTCVendor advisory
  17. 2026-08-18 07:45 UTCGHSA enrichment
  18. 2026-08-17 19:35 UTCEG score recompute
  19. 2026-08-17 19:35 UTCVendor advisory
  20. 2026-08-17 19:35 UTCGHSA enrichment
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-17 05:48 UTCVendor advisory
  23. 2026-08-17 05:48 UTCGHSA enrichment
  24. 2026-08-16 17:43 UTCEG score recompute
  25. 2026-08-16 17:43 UTCVendor advisory
Show 75 more
  1. 2026-08-16 17:43 UTCGHSA enrichment
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 05:37 UTCEG score recompute
  4. 2026-08-16 05:37 UTCVendor advisory
  5. 2026-08-16 05:37 UTCGHSA enrichment
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 17:33 UTCVendor advisory
  8. 2026-08-15 17:33 UTCGHSA enrichment
  9. 2026-08-15 05:28 UTCEG score recompute
  10. 2026-08-15 05:28 UTCVendor advisory
  11. 2026-08-15 05:28 UTCGHSA enrichment
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-14 17:22 UTCVendor advisory
  14. 2026-08-14 17:22 UTCGHSA enrichment
  15. 2026-08-14 05:11 UTCEG score recompute
  16. 2026-08-14 05:11 UTCVendor advisory
  17. 2026-08-14 05:11 UTCGHSA enrichment
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-13 17:06 UTCVendor advisory
  20. 2026-08-13 17:06 UTCGHSA enrichment
  21. 2026-08-13 05:01 UTCVendor advisory
  22. 2026-08-13 05:01 UTCGHSA enrichment
  23. 2026-08-12 16:57 UTCEG score recompute
  24. 2026-08-12 16:57 UTCVendor advisory
  25. 2026-08-12 16:57 UTCGHSA enrichment
  26. 2026-08-12 13:51 UTCEPSS rescore
  27. 2026-08-12 04:52 UTCVendor advisory
  28. 2026-08-12 04:52 UTCGHSA enrichment
  29. 2026-08-11 16:47 UTCVendor advisory
  30. 2026-08-11 16:47 UTCGHSA enrichment
  31. 2026-08-11 04:42 UTCEG score recompute
  32. 2026-08-11 04:42 UTCVendor advisory
  33. 2026-08-11 04:42 UTCGHSA enrichment
  34. 2026-08-11 00:00 UTCEPSS rescore
  35. 2026-08-10 16:37 UTCVendor advisory
  36. 2026-08-10 16:37 UTCGHSA enrichment
  37. 2026-08-10 04:25 UTCVendor advisory
  38. 2026-08-10 04:25 UTCGHSA enrichment
  39. 2026-08-09 16:21 UTCEG score recompute
  40. 2026-08-09 16:21 UTCVendor advisory
  41. 2026-08-09 16:21 UTCGHSA enrichment
  42. 2026-08-09 13:46 UTCEPSS rescore
  43. 2026-08-09 04:16 UTCEG score recompute
  44. 2026-08-09 04:16 UTCVendor advisory
  45. 2026-08-09 04:16 UTCGHSA enrichment
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-08 16:11 UTCVendor advisory
  48. 2026-08-08 16:11 UTCGHSA enrichment
  49. 2026-08-08 04:05 UTCEG score recompute
  50. 2026-08-08 04:05 UTCVendor advisory
  51. 2026-08-08 04:05 UTCGHSA enrichment
  52. 2026-08-07 16:00 UTCVendor advisory
  53. 2026-08-07 16:00 UTCGHSA enrichment
  54. 2026-08-07 03:55 UTCVendor advisory
  55. 2026-08-07 03:55 UTCGHSA enrichment
  56. 2026-08-06 15:50 UTCEG score recompute
  57. 2026-08-06 15:50 UTCVendor advisory
  58. 2026-08-06 15:50 UTCGHSA enrichment
  59. 2026-08-06 13:46 UTCEPSS rescore
  60. 2026-08-06 04:37 UTCEG score recompute
  61. 2026-08-06 04:37 UTCVendor advisory
  62. 2026-08-06 04:37 UTCGHSA enrichment
  63. 2026-08-05 19:17 UTCEPSS rescore
  64. 2026-08-05 16:32 UTCEG score recompute
  65. 2026-08-05 16:32 UTCGHSA enrichment
  66. 2026-08-05 15:30 UTCEG score recompute
  67. 2026-08-05 15:30 UTCGHSA enrichment
  68. 2026-08-05 03:24 UTCGHSA enrichment
  69. 2026-08-04 15:20 UTCEG score recompute
  70. 2026-08-04 15:20 UTCGHSA enrichment
  71. 2026-08-04 15:10 UTCEPSS rescore
  72. 2026-08-04 14:48 UTCEG score recompute
  73. 2026-08-04 14:48 UTCGHSA enrichment
  74. 2026-08-04 04:27 UTCEG score recompute
  75. 2026-08-04 03:34 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-42169?
CVE-2026-42169 is a high vulnerability published on August 4, 2026. 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…
When was CVE-2026-42169 disclosed?
CVE-2026-42169 was first published in the National Vulnerability Database on August 4, 2026, with the most recent update on August 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42169 actively exploited?
CVE-2026-42169 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.7% of all scored CVEs.
What is the CVSS score of CVE-2026-42169?
CVE-2026-42169 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-42169?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42169, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42169

Explore →

Is Your Infrastructure Affected by CVE-2026-42169?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs