A heap-based buffer overflow vulnerability exists in the GIMP DDS (DirectDraw Surface) file parser. When a crafted DDS file declares a D3D9 pixel format but sets a lower bits-per-pixel (bpp) value in the header, the loader allocates an undersized heap buffer. Subsequent pixel data consumption at the real format's stride causes a write past the heap buffer boundary, leading to heap metadata corruption and potential code execution.
CVE-2026-42170
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-08. a secondary CVSS source baseline 7.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(high)
- EG Risk
- 35(Track)EG Risk 35/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 computedSeverity78% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 9%
- KEV
- Not listed
Published
August 8, 2026
Last Modified
August 14, 2026
Advisory Details (2)
Auto-updated Aug 8, 20262461726 – (CVE-2026-42170) CVE-2026-42170 gimp: GIMP DDS plug-in heap-based buffer overflow via BPP mismatch in load_layer() (ddsread.c)
https://bugzilla.redhat.com/show_bug.cgi?id=2461726CVE-2026-42170 - 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-42170Vendor Advisories for CVE-2026-42170(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gimp | 2.10.22-4 ... 3.2.4-3 (61 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gimp | 2.10.34-1 ... 3.2.4-3 (56 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gimp | 3.0.4-3 ... 3.2.4-3 (28 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gimp | 3.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 27× in last 7d / 54× 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.
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 20:21 UTCGHSA enrichment
- 2026-08-20 08:16 UTCGHSA enrichment
- 2026-08-19 20:12 UTCEG score recompute
- 2026-08-19 20:12 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 08:04 UTCGHSA enrichment
- 2026-08-18 19:59 UTCEG score recompute
- 2026-08-18 19:59 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 07:54 UTCGHSA enrichment
- 2026-08-17 19:49 UTCEG score recompute
- 2026-08-17 19:49 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 07:44 UTCGHSA enrichment
- 2026-08-16 19:40 UTCEG score recompute
- 2026-08-16 19:40 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 07:34 UTCEG score recompute
- 2026-08-16 07:34 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 19:30 UTCGHSA enrichment
- 2026-08-15 07:25 UTCEG score recompute
- 2026-08-15 07:25 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
Show 29 moreShow fewer
- 2026-08-14 19:19 UTCGHSA enrichment
- 2026-08-14 15:56 UTCGHSA enrichment
- 2026-08-14 03:52 UTCEG score recompute
- 2026-08-14 03:52 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 15:47 UTCGHSA enrichment
- 2026-08-13 03:42 UTCGHSA enrichment
- 2026-08-12 15:37 UTCEG score recompute
- 2026-08-12 15:37 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 03:33 UTCGHSA enrichment
- 2026-08-11 15:27 UTCEG score recompute
- 2026-08-11 15:27 UTCGHSA enrichment
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 03:23 UTCEG score recompute
- 2026-08-11 03:23 UTCGHSA enrichment
- 2026-08-11 02:19 UTCEG score recompute
- 2026-08-11 02:19 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 16:41 UTCGHSA enrichment
- 2026-08-10 04:36 UTCGHSA enrichment
- 2026-08-09 16:31 UTCEG score recompute
- 2026-08-09 16:31 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 04:27 UTCEG score recompute
- 2026-08-09 04:27 UTCGHSA enrichment
- 2026-08-08 16:22 UTCEG score recompute
- 2026-08-08 15:57 UTCEG score recompute
- 2026-08-08 15:56 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-42170?
When was CVE-2026-42170 disclosed?
Is CVE-2026-42170 actively exploited?
What is the CVSS score of CVE-2026-42170?
How do I remediate CVE-2026-42170?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42170
Is Your Infrastructure Affected by CVE-2026-42170?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.