CVE-2026-58380

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 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.

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 6, 2026

Last Modified

July 16, 2026

Advisory Details (4)

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

GIMP PNM File Parsing Stack Buffer Overflow (#16206) · Issues · GNOME / GIMP · GitLab

https://gitlab.gnome.org/GNOME/gimp/-/issues/16206
generic

Client Challenge

https://gitlab.gnome.org/GNOME/gimp/-/commit/83699817
redhat

2496135 – (CVE-2026-58380) CVE-2026-58380 gimp: gimp: Stack buffer overflow in pnmscanner_gettoken()

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

cve-details

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

Vendor 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.

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.2.4-3 (28 versions)——
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 34× in last 7d / 171× 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 238 total refreshes for this CVE.

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

Frequently asked(5)

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, 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-58380 actively exploited?
CVE-2026-58380 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 83.0% of all scored CVEs.
What is the CVSS score of CVE-2026-58380?
CVE-2026-58380 has a CVSS v3 base score of 7.8 (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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-58380?

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

Start Free Scan →Browse All CVEs