CVE-2026-4887

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 53% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in GIMP. This issue is a heap buffer over-read in GIMP PCX file loader due to an off-by-one error. A remote attacker could exploit this by convincing a user to open a specially crafted PCX image. Successful exploitation could lead to out-of-bounds memory disclosure and a possible application crash, resulting in a Denial of Service (DoS).

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/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
Severity71% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

March 26, 2026

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated May 14, 2026
Patch available. Sources: redhat.
generic

(CVE-2026-4887) Heap buffer overflow read in PCX file loader due to off-by-one in bytesperline validation (#15960) · Issues · GNOME / GIMP · GitLab

https://gitlab.gnome.org/GNOME/gimp/-/issues/15960
redhat Patch Available

2451669 – (CVE-2026-4887) CVE-2026-4887 gimp: GIMP:Memory disclosure and denial of service via specially crafted PCX image

Affected: Red Hat Enterprise Linux 9

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

cve-details

https://access.redhat.com/security/cve/CVE-2026-4887
redhat Patch Available

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:17533
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:16484

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatgimp-2:2.8.22-1.el7_9.62026-06-16redhat
redhatgimp-2:2.99.8-4.el9_6.72026-06-15redhat
redhatgimp-2:2.99.8-4.el9_4.62026-06-15redhat
redhatgimp-2:2.99.8-4.el9_2.62026-06-15redhat
redhatgimp:2.8-8040020260520140422.705845972026-05-26redhat
redhatgimp:2.8-8080020260520102644.0621e4ee2026-05-26redhat
redhatgimp-2:2.99.8-3.el9_0.62026-05-26redhat
redhatgimp:2.8-8060020260520140100.6af1eaf02026-05-26redhat
redhatgimp-2:3.0.4-4.el9_8.42026-05-19redhat
redhatgimp:2.8-8100020260512115927.4c9c024f2026-05-14redhat
redhatgimp-2:3.0.4-1.el9_7.52026-05-12redhat

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.0~RC3-1 (14 versions)3.2.0-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 67× 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 177 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-4887?
CVE-2026-4887 is a high vulnerability published on March 26, 2026. A flaw was found in GIMP. This issue is a heap buffer over-read in GIMP PCX file loader due to an off-by-one error. A remote attacker could exploit this by convincing a user to open a specially crafted PCX image. Successful exploitation could lead to out-of-bounds memory disclosure and a possible…
When was CVE-2026-4887 disclosed?
CVE-2026-4887 was first published in the National Vulnerability Database on March 26, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-4887 actively exploited?
CVE-2026-4887 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.3% of all scored CVEs.
What is the CVSS score of CVE-2026-4887?
CVE-2026-4887 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-4887?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-4887, 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-4887

Explore →

Is Your Infrastructure Affected by CVE-2026-4887?

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