CVE-2026-2046VulnerabilityPublished 16 Mar 2026

ZDI-26-213: GIMP LBM File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability

Source Zero Day Initiative

Compare

Not known to be exploited.

Data as of 26 May 2026, 20:33 UTC

Severity

High

Rated High by Zero Day Initiative · No CVSS score from NVD or the CNA

Exploitation evidence

Disclosed: evidence found.
Public on cve.org; its publication date is not in this record
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

remote

What to do

AI-suggested

An official patch has been released by GIMP to correct this vulnerability. Users and administrators should apply the update from the GIMP GitLab repository (commit b4d41182dde4a1f98431b4d5b749a5a18bed0ab3) or through their standard update channels to remediate this issue. No additional mitigation steps are indicated by the vendor advisory.

Description

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 ZDI has assigned a CVSS rating of 7.8. The following CVEs are assigned: CVE-2026-2046.

Impact

Successful exploitation allows remote attackers to execute arbitrary code with the privileges of the user running GIMP. This can lead to full compromise of the affected system or user environment. The vulnerability requires user interaction, limiting automatic exploitation. The CVSS vector indicates high impact on confidentiality, integrity, and availability.

Summary

CVE-2026-2046 is a heap-based buffer overflow vulnerability in the LBM file parser of GIMP. The flaw is due to insufficient validation of the length of user-supplied data before copying it into a heap buffer, which can lead to arbitrary code execution in the context of the current process. Exploitation requires user interaction, such as opening a crafted malicious LBM file or visiting a malicious page. The vulnerability has a CVSS score of 7.8, indicating high severity. GIMP has issued an official patch to fix this vulnerability, as documented in their GitLab commit b4d41182dde4a1f98431b4d5b749a5a18bed0ab3.

References

zerodayinitiative.com/advisories/ZDI-26-213/ (opens in a new tab)

Community reviews

Loading reviews…