CVE-2026-2050

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

GIMP HDR File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GIMP. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

The specific flaw exists within the parsing of HDR files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-28266.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

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
Severity78% × 45%
Exploitation1% × 40%
Automatability0% × 15%
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

Published

June 24, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
Patch available.
generic

ZDI-26-282 - TrendAI™ Zero Day Initiative™ (ZDI)

https://www.zerodayinitiative.com/advisories/ZDI-26-282/
generic

ZDI-CAN-28266: guard against buffer overflow (!241) · Merge requests · GNOME / gegl · GitLab

https://gitlab.gnome.org/GNOME/gegl/-/merge_requests/241

Vendor Advisories for CVE-2026-2050(4)

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

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatgegl-0:0.2.0-39.el8_4.12026-09-08redhat
redhatgegl-0:0.2.0-39.el8_6.12026-09-08redhat
redhatgegl-0:0.2.0-39.el8_8.12026-09-08redhat
redhatgegl04-0:0.4.34-2.el9_2.12026-08-19redhat
redhatgegl04-0:0.4.34-3.el9_4.12026-08-19redhat
redhatgegl04-0:0.4.34-3.el9_6.12026-08-19redhat
redhatgegl-0:0.2.0-40.el8_102026-07-13redhat
redhatgegl04-0:0.4.62-1.el9_8.12026-07-13redhat

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 rangeFix by version rangeDependents
gegl1:0.4.26-2, 1:0.4.26-2+deb11u1
  • every version up to 1:0.4.26-2+deb11u2: fixed in 1:0.4.26-2+deb11u2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
gegl1:0.4.42-2, 1:0.4.42-2+deb12u1
  • every version up to 1:0.4.42-2+deb12u2: fixed in 1:0.4.42-2+deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
gegl1:0.4.62-2, 1:0.4.62-2+deb13u1
  • every version up to 1:0.4.62-2+deb13u2: fixed in 1:0.4.62-2+deb13u2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
gegl1:0.4.62-2 ... 1:0.4.64-2 (6 versions)
  • every version up to 1:0.4.66-1: fixed in 1:0.4.66-1
—

Weakness Classification(2)

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

Additional Vendor Advisories

(5)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-2050?
CVE-2026-2050 is a high vulnerability published on June 24, 2026. GIMP HDR File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GIMP. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or…
When was CVE-2026-2050 disclosed?
CVE-2026-2050 was first published on June 24, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-2050 actively exploited?
CVE-2026-2050 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-2050?
CVE-2026-2050 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-2050?
A fix for CVE-2026-2050 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-2050 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-2050?

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

Book a Demo →Browse All CVEs