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.
CVE-2026-58384
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.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- 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 computedSeverity78% × 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, 2026GIMP PSD File Parsing Heap Buffer Overflow in RLE Channel Processing (#16216) · Issues · GNOME / GIMP · GitLab
https://gitlab.gnome.org/GNOME/gimp/-/issues/162162497431 – (CVE-2026-58384) CVE-2026-58384 gimp: gimp: Integer overflow in read_RLE_channel()
https://bugzilla.redhat.com/show_bug.cgi?id=2497431Vendor 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 / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | gimp-2:3.0.4-4.el9_8.7 | 2026-07-16 | 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 | 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.0.4-3+deb13u9 (10 versions) | 3.0.4-3+deb13u10 | — |
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.
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.
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 14:09 UTCEG score recompute
- 2026-09-06 14:08 UTCVendor advisory
- 2026-09-06 14:08 UTCGHSA enrichment
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 22:55 UTCEG score recompute
- 2026-09-05 22:55 UTCVendor advisory
- 2026-09-05 22:55 UTCGHSA enrichment
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-30 19:49 UTCEG score recompute
- 2026-08-30 19:49 UTCVendor advisory
- 2026-08-30 19:49 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 07:44 UTCEG score recompute
- 2026-08-30 07:44 UTCVendor advisory
- 2026-08-30 07:44 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 21:56 UTCEG score recompute
Show 75 moreShow fewer
- 2026-08-27 21:56 UTCVendor advisory
- 2026-08-27 21:56 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 02:01 UTCEG score recompute
- 2026-08-27 02:01 UTCVendor advisory
- 2026-08-27 02:01 UTCGHSA enrichment
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 13:49 UTCEG score recompute
- 2026-08-26 13:49 UTCVendor advisory
- 2026-08-26 13:49 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 10:20 UTCVendor advisory
- 2026-08-25 10:20 UTCGHSA enrichment
- 2026-08-24 20:39 UTCEG score recompute
- 2026-08-24 20:39 UTCVendor advisory
- 2026-08-24 20:39 UTCGHSA enrichment
- 2026-08-24 06:32 UTCVendor advisory
- 2026-08-24 06:32 UTCGHSA enrichment
- 2026-08-23 18:08 UTCVendor advisory
- 2026-08-23 18:08 UTCGHSA enrichment
- 2026-08-23 06:03 UTCEG score recompute
- 2026-08-23 06:03 UTCVendor advisory
- 2026-08-23 06:03 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 17:54 UTCVendor advisory
- 2026-08-22 17:54 UTCGHSA enrichment
- 2026-08-22 05:07 UTCEG score recompute
- 2026-08-22 05:07 UTCVendor advisory
- 2026-08-22 05:07 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 17:00 UTCVendor advisory
- 2026-08-21 17:00 UTCGHSA enrichment
- 2026-08-21 04:14 UTCEG score recompute
- 2026-08-21 04:14 UTCVendor advisory
- 2026-08-21 04:14 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 15:40 UTCVendor advisory
- 2026-08-20 15:40 UTCGHSA enrichment
- 2026-08-20 02:20 UTCEG score recompute
- 2026-08-20 02:20 UTCVendor advisory
- 2026-08-20 02:20 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 11:09 UTCVendor advisory
- 2026-08-19 11:09 UTCGHSA enrichment
- 2026-08-18 23:01 UTCEG score recompute
- 2026-08-18 23:01 UTCVendor advisory
- 2026-08-18 23:01 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 10:56 UTCVendor advisory
- 2026-08-18 10:56 UTCGHSA enrichment
- 2026-08-17 22:38 UTCEG score recompute
- 2026-08-17 22:38 UTCVendor advisory
- 2026-08-17 22:38 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 08:13 UTCVendor advisory
- 2026-08-17 08:13 UTCGHSA enrichment
- 2026-08-16 20:08 UTCEG score recompute
- 2026-08-16 20:08 UTCVendor advisory
- 2026-08-16 20:08 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 08:02 UTCEG score recompute
- 2026-08-16 08:02 UTCVendor advisory
- 2026-08-16 08:02 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 19:57 UTCVendor advisory
- 2026-08-15 19:57 UTCGHSA enrichment
- 2026-08-15 07:50 UTCEG score recompute
- 2026-08-15 07:50 UTCVendor advisory
- 2026-08-15 07:50 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 18:14 UTCVendor advisory
- 2026-08-14 18:14 UTCGHSA enrichment
- 2026-08-14 06:08 UTCEG score recompute
- 2026-08-14 06:08 UTCVendor advisory
- 2026-08-14 06:08 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-58384?
When was CVE-2026-58384 disclosed?
Is CVE-2026-58384 actively exploited?
What is the CVSS score of CVE-2026-58384?
How do I remediate CVE-2026-58384?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-58384
Is Your Infrastructure Affected by CVE-2026-58384?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.