A flaw was found in GIMP's PNM file format parser. When parsing a specially crafted PNM file, the pnmscanner_gettoken() function writes a null terminator one byte past the end of a stack-allocated buffer due to an off-by-one error in the loop boundary check. This could lead to memory corruption, potentially resulting in denial of service or arbitrary code execution.
CVE-2026-58380
HIGHPre-NVD 7.37.3—Trending — 3 sources updated this week
EchelonGraph scoreHIGH confidence
Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-07-06. a secondary CVSS source baseline 7.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
7.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 7.3Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.3
- EG Score
- 7.3(high)
- EPSS
- —
- KEV
- Not listed
Published
July 6, 2026
Last Modified
July 6, 2026
Advisory Details (4)
Auto-updated Jul 6, 2026Patch available. Sources: redhat.
generic
GIMP PNM File Parsing Stack Buffer Overflow (#16206) · Issues · GNOME / GIMP · GitLab
https://gitlab.gnome.org/GNOME/gimp/-/issues/16206redhat
2496135 – (CVE-2026-58380) CVE-2026-58380 gimp: gimp: Stack buffer overflow in pnmscanner_gettoken()
https://bugzilla.redhat.com/show_bug.cgi?id=2496135Vendor Advisories for CVE-2026-58380(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× 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-07-07 02:09 UTCEG score recompute
- 2026-07-07 02:09 UTCGHSA enrichment
- 2026-07-06 14:22 UTCEG score recompute
- 2026-07-06 14:21 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-58380?
CVE-2026-58380 is a high vulnerability published on July 6, 2026. A flaw was found in GIMP's PNM file format parser. When parsing a specially crafted PNM file, the pnmscanner_gettoken() function writes a null terminator one byte past the end of a stack-allocated buffer due to an off-by-one error in the loop boundary check. This could lead to memory corruption,…
When was CVE-2026-58380 disclosed?
CVE-2026-58380 was first published in the National Vulnerability Database on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-58380?
CVE-2026-58380 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-58380?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58380, 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
Explore the affected products and dependency analysis for CVE-2026-58380
Is Your Infrastructure Affected by CVE-2026-58380?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.