A flaw was found in GIMP's Paint Shop Pro (PSP) file format parser. This heap buffer overflow vulnerability allows a remote attacker to cause arbitrary code execution or a denial of service (DoS) by tricking a user into opening a specially crafted PSP image file. The vulnerability occurs because the software incorrectly calculates buffer sizes when processing low bit-depth images, leading to an overwrite of adjacent memory.
CVE-2026-58379
Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-07-03. a secondary CVSS source baseline 7.3; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.3
- EG Score
- 7.3(medium)
- 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 computedSeverity73% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 14%
- KEV
- Not listed
Published
July 3, 2026
Last Modified
July 13, 2026
Advisory Details (4)
Auto-updated Jul 3, 2026GIMP PSP File Parsing Heap Buffer Overflow (Patch Bypass of CVE-2026-4153) (#16205) · Issues · GNOME / GIMP · GitLab
https://gitlab.gnome.org/GNOME/gimp/-/issues/162052495997 – (CVE-2026-58379) CVE-2026-58379 gimp: gimp: Heap buffer overflow in read_channel_data()
https://bugzilla.redhat.com/show_bug.cgi?id=2495997Vendor Advisories for CVE-2026-58379(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.5 | 2026-07-13 | 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.4-3 (19 versions) | — | — |
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 / 106× 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 286 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:17 UTCEG score recompute
- 2026-09-06 14:17 UTCVendor advisory
- 2026-09-06 14:17 UTCGHSA enrichment
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 23:44 UTCEG score recompute
- 2026-09-05 23:44 UTCVendor advisory
- 2026-09-05 23:44 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 23:27 UTCEG score recompute
- 2026-08-30 23:27 UTCVendor advisory
- 2026-08-30 23:27 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 11:18 UTCEG score recompute
- 2026-08-30 11:18 UTCVendor advisory
- 2026-08-30 11:18 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 22:12 UTCEG score recompute
Show 75 moreShow fewer
- 2026-08-27 22:12 UTCVendor advisory
- 2026-08-27 22:12 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 02:59 UTCEG score recompute
- 2026-08-27 02:59 UTCVendor advisory
- 2026-08-27 02:59 UTCGHSA enrichment
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 14:33 UTCEG score recompute
- 2026-08-26 14:33 UTCVendor advisory
- 2026-08-26 14:32 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 13:38 UTCVendor advisory
- 2026-08-25 13:38 UTCGHSA enrichment
- 2026-08-24 22:12 UTCEG score recompute
- 2026-08-24 22:12 UTCVendor advisory
- 2026-08-24 22:12 UTCGHSA enrichment
- 2026-08-24 10:12 UTCEG score recompute
- 2026-08-24 10:12 UTCVendor advisory
- 2026-08-24 10:12 UTCGHSA enrichment
- 2026-08-23 19:09 UTCVendor advisory
- 2026-08-23 19:09 UTCGHSA enrichment
- 2026-08-23 07:09 UTCEG score recompute
- 2026-08-23 07:09 UTCVendor advisory
- 2026-08-23 07:09 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 19:08 UTCVendor advisory
- 2026-08-22 19:08 UTCGHSA enrichment
- 2026-08-22 05:55 UTCEG score recompute
- 2026-08-22 05:55 UTCVendor advisory
- 2026-08-22 05:55 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 17:14 UTCVendor advisory
- 2026-08-21 17:14 UTCGHSA enrichment
- 2026-08-21 04:25 UTCEG score recompute
- 2026-08-21 04:25 UTCVendor advisory
- 2026-08-21 04:25 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 15:51 UTCVendor advisory
- 2026-08-20 15:51 UTCGHSA enrichment
- 2026-08-20 03:42 UTCEG score recompute
- 2026-08-20 03:42 UTCVendor advisory
- 2026-08-20 03:42 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 12:32 UTCVendor advisory
- 2026-08-19 12:32 UTCGHSA enrichment
- 2026-08-18 23:48 UTCEG score recompute
- 2026-08-18 23:48 UTCVendor advisory
- 2026-08-18 23:47 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 11:45 UTCVendor advisory
- 2026-08-18 11:45 UTCGHSA enrichment
- 2026-08-17 22:47 UTCEG score recompute
- 2026-08-17 22:47 UTCVendor advisory
- 2026-08-17 22:47 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 06:06 UTCVendor advisory
- 2026-08-17 06:06 UTCGHSA enrichment
- 2026-08-16 18:04 UTCEG score recompute
- 2026-08-16 18:04 UTCVendor advisory
- 2026-08-16 18:04 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 05:29 UTCEG score recompute
- 2026-08-16 05:29 UTCVendor advisory
- 2026-08-16 05:29 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 17:29 UTCVendor advisory
- 2026-08-15 17:29 UTCGHSA enrichment
- 2026-08-15 05:27 UTCEG score recompute
- 2026-08-15 05:27 UTCVendor advisory
- 2026-08-15 05:27 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 17:26 UTCVendor advisory
- 2026-08-14 17:26 UTCGHSA enrichment
- 2026-08-14 05:13 UTCEG score recompute
- 2026-08-14 05:13 UTCVendor advisory
Frequently asked(5)
What is CVE-2026-58379?
When was CVE-2026-58379 disclosed?
Is CVE-2026-58379 actively exploited?
What is the CVSS score of CVE-2026-58379?
How do I remediate CVE-2026-58379?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-58379
Is Your Infrastructure Affected by CVE-2026-58379?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.