Live › vulnerability › CVE-2026-92183
Go to dashboardGIMP mishandles the length of data read from an APNG image, copying it into a fixed stack buffer without a bounds check. An attacker who gets a user to open or view a crafted file can run code in the GIMP process.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Any installation of GIMP that parses APNG files can be affected, most often on desktops where users open images downloaded from the web or email. Systems where GIMP is not installed, or where users only open trusted files, have less exposure. The sources do not name specific versions.
No product ranges from the sources yet.
gimp --version on each workstation or server that has GIMP installed and compare against the fixed release.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
GIMP APNG File Parsing Stack-based Buffer 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 APNG files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-29400.
This page as .md · .json · in your agent: get_signal("CVE-2026-92183")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.