A flaw was found in the file-fits plugin in GIMP. When processing a FITS image file, the plugin calculates memory allocation sizes using signed 32-bit integers for width and height. If a crafted file sets both values to large values, their product exceeds 2^31 and overflows, resulting in an undersized heap-based buffer allocation. This integer overflow issue results in a heap-based buffer overflow when cfitsio subsequently writes a full row of pixels in the buffer, causing memory corruption, potentially leading to arbitrary code execution or a denial of service.
CVE-2026-66758
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-27. a secondary CVSS source baseline 7.8; sources differ by 0.0.
- 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
- 22%
- KEV
- Not listed
Published
July 27, 2026
Last Modified
September 2, 2026
Advisory Details (3)
Auto-updated Jul 27, 20263 memory corruption vulnerabilities in GIMP's file format loaders (#16528) · Issues · GNOME / GIMP · GitLab
https://gitlab.gnome.org/GNOME/gimp/-/issues/165282507475 – (CVE-2026-66758) CVE-2026-66758 gimp: integer overflow in file-fits plugin causes a heap-based buffer overflow on crafted FITS images
https://bugzilla.redhat.com/show_bug.cgi?id=2507475Vendor Advisories for CVE-2026-66758(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | gimp:2.8-8100020260824165450.4c9c024f | 2026-09-02 | redhat |
| redhat | gimp-2:3.0.4-4.el9_8.9 | 2026-08-05 | 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.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 30× in last 7d / 141× 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 258 total refreshes for this CVE.
- 2026-09-15 09:08 UTCEG score recompute
- 2026-09-15 09:08 UTCVendor advisory
- 2026-09-15 09:08 UTCGHSA enrichment
- 2026-09-14 08:41 UTCVendor advisory
- 2026-09-14 08:41 UTCGHSA enrichment
- 2026-09-13 20:51 UTCEG score recompute
- 2026-09-13 20:51 UTCVendor advisory
- 2026-09-13 20:51 UTCGHSA enrichment
- 2026-09-13 08:34 UTCVendor advisory
- 2026-09-13 08:34 UTCGHSA enrichment
- 2026-09-12 20:45 UTCEG score recompute
- 2026-09-12 20:45 UTCVendor advisory
- 2026-09-12 20:45 UTCGHSA enrichment
- 2026-09-12 08:49 UTCVendor advisory
- 2026-09-12 08:49 UTCGHSA enrichment
- 2026-09-11 20:27 UTCEG score recompute
- 2026-09-11 20:27 UTCVendor advisory
- 2026-09-11 20:27 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-11 08:37 UTCVendor advisory
- 2026-09-11 08:37 UTCGHSA enrichment
- 2026-09-10 20:47 UTCEG score recompute
- 2026-09-10 20:47 UTCVendor advisory
- 2026-09-10 20:47 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-09-10 08:13 UTCVendor advisory
- 2026-09-10 08:13 UTCGHSA enrichment
- 2026-09-09 08:18 UTCEG score recompute
- 2026-09-09 08:18 UTCVendor advisory
- 2026-09-09 08:18 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 21:03 UTCEG score recompute
- 2026-09-07 21:03 UTCVendor advisory
- 2026-09-07 21:03 UTCGHSA enrichment
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 23:27 UTCEG score recompute
- 2026-09-06 23:27 UTCVendor advisory
- 2026-09-06 23:27 UTCGHSA enrichment
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 07:41 UTCVendor advisory
- 2026-09-06 07:41 UTCGHSA enrichment
- 2026-09-05 19:14 UTCEG score recompute
- 2026-09-05 19:14 UTCVendor advisory
- 2026-09-05 19:14 UTCGHSA enrichment
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-05 05:45 UTCEG score recompute
- 2026-09-05 05:45 UTCVendor advisory
- 2026-09-05 05:45 UTCGHSA enrichment
- 2026-09-04 12:18 UTCEG score recompute
- 2026-09-04 12:18 UTCVendor advisory
- 2026-09-04 12:18 UTCGHSA enrichment
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-02 10:23 UTCEG score recompute
- 2026-09-02 10:23 UTCVendor advisory
- 2026-09-02 10:23 UTCGHSA enrichment
- 2026-09-02 09:46 UTCEG score recompute
- 2026-09-02 09:46 UTCVendor advisory
- 2026-09-02 09:45 UTCGHSA enrichment
- 2026-09-01 22:58 UTCEG score recompute
- 2026-09-01 22:58 UTCVendor advisory
- 2026-09-01 22:58 UTCGHSA enrichment
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-09-01 01:01 UTCVendor advisory
- 2026-09-01 01:01 UTCGHSA enrichment
- 2026-08-30 23:30 UTCEG score recompute
- 2026-08-30 23:30 UTCVendor advisory
- 2026-08-30 23:30 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 11:40 UTCEG score recompute
- 2026-08-30 11:40 UTCVendor advisory
- 2026-08-30 11:40 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 23:50 UTCEG score recompute
- 2026-08-29 23:50 UTCVendor advisory
- 2026-08-29 23:50 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 21:31 UTCEG score recompute
- 2026-08-27 21:31 UTCVendor advisory
- 2026-08-27 21:31 UTCGHSA enrichment
- 2026-08-27 09:42 UTCEG score recompute
- 2026-08-27 09:42 UTCVendor advisory
- 2026-08-27 09:42 UTCGHSA enrichment
- 2026-08-26 19:44 UTCEG score recompute
- 2026-08-26 19:44 UTCVendor advisory
- 2026-08-26 19:44 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 06:50 UTCVendor advisory
- 2026-08-26 06:50 UTCGHSA enrichment
- 2026-08-25 18:33 UTCEG score recompute
- 2026-08-25 18:33 UTCVendor advisory
- 2026-08-25 18:33 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 06:40 UTCVendor advisory
- 2026-08-25 06:40 UTCGHSA enrichment
- 2026-08-24 18:44 UTCEG score recompute
- 2026-08-24 18:44 UTCVendor advisory
- 2026-08-24 18:44 UTCGHSA enrichment
- 2026-08-24 06:55 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-190
Frequently asked(5)
What is CVE-2026-66758?
When was CVE-2026-66758 disclosed?
Is CVE-2026-66758 actively exploited?
What is the CVSS score of CVE-2026-66758?
How do I remediate CVE-2026-66758?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-66758
Is Your Infrastructure Affected by CVE-2026-66758?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.