CVE-2026-4151

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-11. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.8EG
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.8Exploit: None knownExposed: 0

A fix is available — apply it.

GIMP ANI File Parsing Integer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GIMP. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

The specific flaw exists within the parsing of ANI files. The issue results from the lack of proper validation of user-supplied data, which can result in an integer overflow before allocating a buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-28813.

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%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

April 11, 2026

Last Modified

July 15, 2026

Advisory Details (2)

Auto-updated Jun 10, 2026
No patch confirmed yet.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatgimp-2:3.0.4-4.el9_8.42026-05-19redhat
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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
gimp3.0.4-3 ... 3.0.4-3+deb13u7 (8 versions)3.0.4-3+deb13u8
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 4× in last 7d / 24× 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 199 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-4151?
CVE-2026-4151 is a high vulnerability published on April 11, 2026. GIMP ANI File Parsing Integer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GIMP. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a…
When was CVE-2026-4151 disclosed?
CVE-2026-4151 was first published in the National Vulnerability Database on April 11, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-4151 actively exploited?
CVE-2026-4151 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 50.2% of all scored CVEs.
What is the CVSS score of CVE-2026-4151?
CVE-2026-4151 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-4151?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-4151, 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-4151

Explore →

Is Your Infrastructure Affected by CVE-2026-4151?

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