CVE-2026-58384

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 83% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
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%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in GIMP's PSD parser. An integer overflow in read_RLE_channel() can cause an undersized heap allocation for the RLE row-length table, after which subsequent per-row writes corrupt heap memory. This could lead to memory corruption, potentially resulting in denial of service or arbitrary code execution.

CVSS v3
7.8
EG Score
7.8(medium)
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 computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

July 7, 2026

Last Modified

July 16, 2026

Advisory Details (4)

Auto-updated Jul 7, 2026
Patch available. Sources: redhat.
generic

GIMP PSD File Parsing Heap Buffer Overflow in RLE Channel Processing (#16216) · Issues · GNOME / GIMP · GitLab

https://gitlab.gnome.org/GNOME/gimp/-/issues/16216
redhat

2497431 – (CVE-2026-58384) CVE-2026-58384 gimp: gimp: Integer overflow in read_RLE_channel()

https://bugzilla.redhat.com/show_bug.cgi?id=2497431
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-58384

Vendor Advisories for CVE-2026-58384(1)

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.72026-07-16redhat

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.0.4-3+deb13u9 (10 versions)3.0.4-3+deb13u10
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.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-58384?
CVE-2026-58384 is a high vulnerability published on July 7, 2026. A flaw was found in GIMP's PSD parser. An integer overflow in readRLEchannel() can cause an undersized heap allocation for the RLE row-length table, after which subsequent per-row writes corrupt heap memory. This could lead to memory corruption, potentially resulting in denial of service or…
When was CVE-2026-58384 disclosed?
CVE-2026-58384 was first published in the National Vulnerability Database on July 7, 2026, with the most recent update on July 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58384 actively exploited?
CVE-2026-58384 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 82.6% of all scored CVEs.
What is the CVSS score of CVE-2026-58384?
CVE-2026-58384 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-58384?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58384, 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-58384

Explore →

Is Your Infrastructure Affected by CVE-2026-58384?

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